Merge all the station monitoring and mitigation into a single service. #874
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This is an attempt to unify all the station monitoring and make it work better as one. We're trying to square a circle here somewhat, with taking steps to kick nodes when problems are detected, but not kick them too quickly or often in case we're mis-identifing issues. We've seen these issue manifest themselves which nodes messing VoIP services as well as resets causing nodes to get into unrecoverable states when there was no real problems in the first place. This will probably need to evolve before the next release, but would be good to get some milage on the new code.
|
There's also more stats recorded and the info included in the support tool data dump. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is an attempt to unify all the station monitoring and make it work better as one. We're trying to square a circle here somewhat, with taking steps to kick nodes when problems are detected, but not kick them too quickly or often in case we're mis-identifing issues.
We've seen these issue manifest themselves which nodes messing VoIP services as well as resets causing nodes to get into unrecoverable states when there was no real problems in the first place.
This will probably need to evolve before the next release, but would be good to get some milage on the new code.