-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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] transport: http2Client.notifyError got notified that the client transport was broken EOF. #500
Comments
I think the underlying grpc connection is broken, but |
I believe this may be related to #499. We don't have a fix yet. You say that MessageIterator.Next doesn't return an error -- does it just hang? If so, one quick solution is to run Next with a timeout, and restart the subscription if you hit it. We're building an improved stream-based implementation of Pull, which may also help. |
Yes, right. MessageIterator.Next() just hang. |
You don't need to pass a timeout to Next. Do something like the following (untested): First, create a context that you can cancel:
Use that context in your call to Pull:
Run your call to Next with a timeout:
|
Yes, I got your point. |
Just jumping into this thread. I'm experiencing the same issue and I'll be trying out the |
Restarting the subscription doesn't seem to be enough. |
Is there any update on this? In a simple |
I think this is a serious bug and I'm still using the hack with cancel, but we have to keep reconnecting unnecessarily depending on traffic. |
Got same issue, no error received, just in the logs: Update: any reasonable hack to keep using |
had a look at how grpc client is initialised and remembered that I have already seen this issue some time ago in my other project. Since it's a grpc client issue - you won't be able to fix it in pubsub package as there are any errors returned by the grpc connection. Fix it by adding additional dialer:
and initialise pubsub client with it:
|
I'm assuming that our new streaming pull implementation and/or the dialer mentioned in the previous comment solve this problem. |
Hello,
My job is pulling messages from pubsub. It works fine until we get an error message like
transport: http2Client.notifyError got notified that the client transport was broken EOF.
.Actually I'm not sure where this error message come from, but once the job gets this message,
it never receives a new message from pubsub (from
next()
call). And the job just keeps writing this error message.Is there any way to debug this?
(I'm using the commit
9d965e63e8cceb1b5d7977a202f0fcb8866d6525
)Thanks,
The text was updated successfully, but these errors were encountered: