-
Notifications
You must be signed in to change notification settings - Fork 227
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.
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
Subscription is not automatically listening for new messages #1658
Comments
I believe I am having similar/same issue. Getting about 50-75 messages on the subscription, then the connection goes idle. Tried both Meanwhile, the topic still contains > 1000 unacked messages. When I restart the subscription, it gets another 50-75 messages, and does the same thing. I am using the default topic and subscription configuration with an extended acknowledgement deadline. |
Using
|
Hmm, I wonder if (like #1665) the acks don't seem to be going through. The server side itself does some flow control, and it would probably stop delivering messages if it's not receiving acks, which does seem to line up with the delivery behaviour. If either of you have a support contract, it might be useful to have someone look at what's happening on the back end. Out of curiosity, do either of you see the same issue if you go back to 3.0.x? I'm trying to figure out if there was a library regression during the exactly once delivery updates. |
We are also facing the same issue where the subscriber client randomly stop pulling in new messages. Environment
What is weird is that not all subscriptions are facing this problem and some subscriptions stop more often than other. Right now we have to manually restart our backend application which is not ideal at all. Examples |
same issue here |
Any updates on this? We are hitting the same issue here |
updates? |
In regards to subscriptions randomly stopping, that's a long term issue we've been looking for solutions for, and we might've found some recently in the latest 4.x branch updates, with grpc keepalives. If possible, try the 4.x branch (requires Node 14, but otherwise basically the same as 3.x), and if problems are still happening, please file a support ticket, as we will likely need to take a look at your specific config and logs. |
Thanks for stopping by to ask us a question! Please make sure to include:
What you're trying to do:
I'm trying to read a subscription. However, when starting the process it receives some messages that are already published and after it is "idle", stopped, doing nothing. Wouldn't that be similar to Go or Java, where it runs and listens for messages being posted?
What code you've already tried:
Any error messages you're getting:
I don't get an error, but I had to write this code below to let my CLI/Batch application listen for messages....but it doesn't seem like a good solution :(
PLEASE READ: If you have a support contract with Google, please create an issue in the support console instead of filing on GitHub. This will ensure a timely response.
The text was updated successfully, but these errors were encountered: