You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: