Identify stale WebSockets #394
Draft
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.
High Level Overview of Change
This PR fixes #390.
Every message transmission through a Websocket is used as its heartbeat signal. If a Websocket has not communicated in the last one minute, then it has failed to transmit ~20 validated ledgers in the ensuing downtime. Such Websockets are categorised as
staleand removed from theconnection_healthtable.Context of Change
Type of Change
None of the APIs have been modified as a part of this PR.
Test Plan