Setting ReadDeadline every time we receive an incoming message #972
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reviewers
r? @bernerd-stripe
cc @stripe/developer-products
Summary
I noticed that we were seeing an decrease in ACKs as the # of event we sent from the backend server went up. I was able to find logs from the CLI side that indicated that the read deadline was exceeded:
When we have a lot of real messages incoming, the backend prioritizes those over the pongs. However, the CLI was only re-setting the deadlines on Pongs and not incoming messages. This change moves the deadline setting logic to within the read loop.
Testing
I reproduced this by disabling pongs from the server.
With no incoming message, we establish connection at 12:04:21 and get a read error at 12:04:31
With an incoming message, we connect at 12:04:54 and get a read error at 12:05:06. 10 seconds after the incoming message.