Implement decommission state for Multi Master Nodes exceeding the range limit of 3. #152
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
Merge Dev Branch into Master for New Hardfork-18
Merge Updated BNS Functionality Code from Dev Branch
Merge BNS Functionality Code from Dev Branch
bump version 5.0.1 from Dev
Merge V5.0.2 from Dev
…ree instances on the same IP.
sanada08
approved these changes
May 7, 2024
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 functionality is introduced to detect when the number of Multi Master Nodes exceeds three within the same IP. When this threshold is surpassed, the system automatically triggers a decommission state for the exceeded range of nodes.