-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Pubsub consumers regularly fill with InvalidArgument #4771
Comments
Got a different error now Code:
Stack trace
|
Some more info, I am now getting Unknown: None Stream removed from future.result() in about 15 minutes regularly.
The subsequent error on subscriber.stop could be due to a custom thread handler I have, I guess the consumer still looks for the built in one.
|
@sachin-shetty Can you give us a bit more details? What did you change between these comments to get these different errors? |
I can not reproduce this error and it's been 2 weeks since the last reply. I'm going to close this for now, but happy to re-open if it's still an issue. |
Google Pubsub Python Client
Linux: 3.10.0-693.5.2.el7.x86_64 #1 SMP Fri Oct 20 20:32:50 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
Python 2.7.5
After a while consumer stops receiving messages, and then I see the above error in the log.
Sometimes the error goes away on closing and re-opening the subscription, sometimes it comes back sooner.
Is there any workaround to monitor the state of the pull subscription and then gracefully restart it?
The text was updated successfully, but these errors were encountered: