-
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
Error: 13 INTERNAL: Received RST_STREAM with error code 2 #437
Comments
@ThomWright thanks for the write up! That error is actually the default error returned from PubSub when they close a stream. The reason it occurs after 30 minutes is because thats when PubSub tends to kill off any streaming connections. When you see this error do messages continue to come in? Or does the Subscription stop functioning altogether? |
That's difficult to say, when one of our services detects an error from a subscription it starts failing health checks and gets restarted pretty soon after. Even if messages could continue to arrive, I'd be unlikely to see them. After rolling back to |
@callmehiphop Subscription stops functioning altogether for me. I've only seen this error on |
I just made a release ( |
That seems to have fixed it, thanks. |
I still see the issue happening once a while with 2.5.0 and it does not look like an issue with one GCP service or client. |
After upgrading to
0.23.0
(from0.21.1
) I see my subscriber services connecting to pubsub, receiving a few messages, then some time later experiencing the following error:Here are some example logs and timestamps from service start until the error:
It seems to take about half an hour from a service starting to receiving the error, reasonably consistently I think.
See googleapis/google-cloud-node#2619 for a similar, previous error.
Environment details
@google-cloud/pubsub
version: 0.23.0Steps to reproduce
0.23.0
Sorry I don't have any better repro steps.
The text was updated successfully, but these errors were encountered: