gitlab-ci-pipelines-exporter icon indicating copy to clipboard operation
gitlab-ci-pipelines-exporter copied to clipboard

Published 20 hours ago • verified publisher icon mvisonneau

taskqredisq: pending failed: redisq: can't find pending message

Open jinvin opened this issue 1 year ago • 5 comments

Hi ,

I'm receiving this error when I try to add more projects to the running Gitlab-exporter with the helm values. For eg: from the below existing projects to projects: - name: foo/bar

project:

  • name: foo/bar1

  • name: foo/bar2

  • name: foo/bar3

    Error : taskqredisq: pending failed: redisq: can't find pending message

    Any idea ?

jinvin avatar Feb 27 '23 09:02 jinvin

I also see this error message, although we are only monitoring a single project with a lot of activity. Version: 0.5.4 via Helm chart

aaronborden-rivian avatar Mar 06 '23 22:03 aaronborden-rivian

same for me

ubershloder avatar Mar 29 '23 11:03 ubershloder

restarting redis (or maybe flushing the queue) fixes it, I wish it would recover it self when it cannot get pending message. Otherwise any restart can block it completely.

Stazis555 avatar May 03 '23 11:05 Stazis555

Same issue for me...

I get a bunch of redisq: can't find pending message id followed by context canceled.

time="2024-06-11T19:22:25Z" level=warning msg="taskq\"msg\"=\"redisq: scheduler failed\" \"error\"=\"redisq: can't find pending message id=\\\"1717709520071-0\\\" in stream=\\\"taskq:{default}:stream\\\"\" \"name\"=\"pending\""
time="2024-06-11T19:22:37Z" level=warning error="context canceled"

I am using GCP Memory Store. Restarting the instance is not something I can consider.

ledouxpl avatar Jun 11 '24 19:06 ledouxpl

Using the exact same configuration and topology but with an in-cluster redis instance made it work.

ledouxpl avatar Jun 15 '24 12:06 ledouxpl