-
Notifications
You must be signed in to change notification settings - Fork 4.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
Ghost message appear on server #150
Comments
This should not happen if the interval between step 2 and 4 is long enough. I am on vacation this week and will try to look into it sometime next week On Mon, Apr 6, 2015 at 7:22 PM, prazzt notifications@github.com wrote:
|
Ahh okay, just enjoy your holiday man .. :)
How long is long enough ? Where is this number defined ? |
I added a gist to help debugging. In my test, after turning of network about 2.5 minutes, message won't be retransmitted. Is this expected ? how can I control the period ? |
I had difficulty to reproduce it. Are you sure the client's main existed before the network connection is on? |
Yes, I'm sure. I just reinstalled all dependencies (grpc, protobuf) just in case.
Steps:
|
If it helps, netstat says FIN_WAIT1 on machine1 while connection's off. |
According to this
Can you try and turn the network only after the socket on the client side no longer exists? I believe the timeout on a standard Linux system is 2 minutes. |
On Thu, Apr 16, 2015 at 6:42 AM, prazzt notifications@github.com wrote:
|
A simple ping pong rpc with increasing counter. Client send ping every n seconds interval, specifying timeout on context.
What happened:
Expected:
Server shouldn't receive message, since client process already exit.
Seems like low level retransmission problem. I'm not familiar with HTTP2 protocol.
The text was updated successfully, but these errors were encountered: