This repository has been archived by the owner on Jul 10, 2024. It is now read-only.
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.
[POA-155] Capture client/server timeouts as well as Agent parsing errors #245
base: main
Are you sure you want to change the base?
[POA-155] Capture client/server timeouts as well as Agent parsing errors #245
Changes from 2 commits
bbad830
a810d14
eba7fd8
65409f6
405def1
03b07fa
d84c32c
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do think it is important to handle RST too, or at least leave a FIXME about abnormal termination.
If the server crashes hard (a kernel failure) or there is a load balancer problem directing traffic to the wrong server, then the client will get a RST back instead of a FIN. Of course, we might not be still around to see the traffic in that case.
The server getting a RST is a bit more obscure.
The comments here do not make it clear how we handle the FIN-ACK from the side that did not initiate the shutdown.