Skip to content
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

Get a "EOF" error after the client dialed grpc server with keep-alive parameters #3091

Closed
lrouter opened this issue Oct 12, 2019 · 2 comments

Comments

@lrouter
Copy link

lrouter commented Oct 12, 2019

We use the keep-alive paramter when dialing to the grpc stream server. After the connection is set up and sent few requests to the server, the client always get a "EOF" error.
If I remove it, it's ok.
I use grpc bidirectional stream mode. The client dialing code is as following:
s.datapathManagerConn, err = s.Dial(s.cfg.Manager.DatapathManager, grpc.WithInitialConnWindowSize(256*1024), grpc.WithUnaryInterceptor( grpc_retry.UnaryClientInterceptor(grpc_retry.WithMax(5))))
Keep-alive parameter is added at the end.
Why ?
I use tcpdump to check the communication. I found that the previous tcp connection would be closed by the client. And the client will re initiate a new tcp connection for keep-alive.

@easwars
Copy link
Contributor

easwars commented Oct 15, 2019

Could you please let us know the exact keepalive.ClientParameters you use on the client.

And did you configure any keepalive.ServerParameters on the server? And how about keepalive.EnforcementPolicy on the server?

@easwars
Copy link
Contributor

easwars commented Oct 15, 2019

Closing this and using #3093 which has more information.

@easwars easwars closed this as completed Oct 15, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Apr 15, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants