-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 DEADLINE_EXCEEDED (after period of inactivity) #1797
Comments
This sounds suspiciously like issues that have been seen with grpc in other languages. |
Yes I saw them when I googled. It is super weird as it happens when there is low traffic |
We will be upgrading to grpc 1.2 soon: #1691 ; If the issue is fixed by that, then there would be no work to be done. |
ok thanks, but will that be with the new pubsub api only or also for 0.5.1? |
It would be put into master, so it would only be available in the release it was added to, or later releases. Since this library is not GA, we are not patching previous releases yet. |
Marking as blocked (grpc 1.2 upgrade) |
After we upgrade to 1.2, in order to see if this is fixed, we need to make sure that calls are successful after long periods of inactivity (at least an hour). |
It will be hard for us to help testing as we require thread limitations for our pubsub implementation (see #1827) and we haven't migrated to the new API. |
The latest release of google-cloud-pubsub now depends on grpc 1.2. |
Removing the release-blocking label because we don't have a repro case. |
Since we don't have a repro case, I'm going to close this out. If the issue is still happening on the latest google-cloud-java (note: we are on grpc 1.4 now), please re-open. |
We see a strange behaviour in when there is low traffic on a topic where stackdriver shows a spike in undelivered messages as well as oldest unacknowledged message.
We do get some io.grpc.StatusRuntimeExceptions during these low traffic times but not when there is high traffic during the day.
Could comeone have an explaination about this? We are using
-netty-all 4.1.5.Final
The text was updated successfully, but these errors were encountered: