-
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
v0.25.0 with grpcio==1.3.5 hangs in completion_queue.poll() #3450
Comments
@yaalaa Thanks for taking the time to report this! Which subpackage are you using (other than just |
Here's the
|
I've looked at the logs. Sometimes it's hard to describe an use-case. Here's an example of how worker feels at the end:
|
I suppose each worker timeout is preceded by |
We have the same issue (and indeed grpcio==1.3.0 fix it) |
@tcroiset Which subpackage are you using? (Is it |
It's google-cloud It's part of a big project but I'll try by tomorrow to extract only the relevant code and reproduce the issue |
Thanks @tcroiset. It's worth pointing out that
So in general, you may be happier being explicit with the |
We've known for a while that gRPC Python doesn't yet play nicely with gevent (and gunicorn? I don't know as much about gunicorn), but the most likely change responsible for what you're seeing is pull request 11154. It added a use of @kpayson64, anything to add that I've missed? |
Thanks for the pointers @nathanielmanistaatgoogle |
As this seems to be an upstream dependency issue, closing here. |
Hi, gapic-google-cloud-datastore-v1==0.15.3 |
I'm not sure that's the right place to file this issue. It could be something well-known one of another project. Nevertheless here it is:
I'm running Google App Engine Flexible VM.
The webservice uses
gunicorn
+gevent
+flask
chain.It uses this lib v0.25.0
Yesterday, upon new deployment, I've faced with old and relatively seldom issue - it hangs in
completion_queue.poll()
in deep ofgrpcio
.I have been seeing such an issue from time to time.
However it has become a nightmare with recent deployment. Workers end up in critical timeout and been rebooted all the way.
And here's what I've found out:
grpcio==1.3.5
- it hangs all the waygrpcio==1.3.0
and things go well.The text was updated successfully, but these errors were encountered: