ReplicaSetStatus: added feature to remove nodes dynamically #9
Conversation
This file contains hidden or 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
added 12 commits
October 18, 2010 19:42
…opyOnWriteArrayList ( in order to support removal of nodes dynamically; admins might change the replica set config ) + equals, hashCode for class Node + adopted method close: set _close to true - Random ( should not be necessary since we iterate all nodes anyway )
…ion as often as possible )
NathanQingyangXu
added a commit
that referenced
this pull request
Mar 29, 2025
… the new test case #9
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.
Hello,
I added the support for removing nodes dynamically; therefore, I changed the Updater-Thread to only take hosts from primary node into account; if the admin of the database removes nodes from the replica set configuration, these nodes will be removed.
I also removed the internal random-mechanism in method "getASecondary", because, for getting the node with the best ping, all nodes are iterated anyway.
Please let me know if it was helpful for you.
Greets, Christoph