Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

pubsub: undelivered messages never pulled #525

Closed
habibrosyad opened this issue Feb 21, 2017 · 1 comment
Closed

pubsub: undelivered messages never pulled #525

habibrosyad opened this issue Feb 21, 2017 · 1 comment
Assignees
@jba
Labels
api: pubsub Issues related to the Pub/Sub API. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@habibrosyad
Copy link

habibrosyad commented Feb 21, 2017 •
edited
Loading

This is happen several times in my case, when I ran several pulls concurrently each with different topics. The undelivered messages just stay in there although i've tried to restart the subscription or making a new one. The strange thing is when there are new messages sent to the topic, the iterator start pulling again. But those remaining messages just still there and never get pulled. Also, the undelivered messages count has peculiarity, it is always even, for example 500, 1000, 2000. Bellow attached a screenshot from StackDriver of this problem. I'm using commit 6521623

pubsub
(undelivered messages metrics)
@rakyll rakyll changed the title [pubsub] undelivered messages never pulled pubsub: undelivered messages never pulled Feb 22, 2017
@jba jba self-assigned this Mar 15, 2017
@jba jba added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. api: pubsub Issues related to the Pub/Sub API. labels Mar 15, 2017
@pongad
Copy link
Contributor

pongad commented Jul 10, 2017

This looks a lot like #684. I believe the part relevant to this issue is already resolved.

@pongad pongad closed this as completed Aug 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jba jba

Labels
api: pubsub Issues related to the Pub/Sub API. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@pongad @habibrosyad @jba