Do not recommend logical config server DNS names for CSRS #2544
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
The idea of having logical DNS names for the config servers only applies the old-style triplet of config servers. The rationale for it is being able to redirect the logical DNS name mapping to another host, in order to "swap out" one of the 3 config servers. However, in the context of config servers *as replsets*, this is bad advice - any situation where you would "swap out" an old-style config server, with CSRS you should instead just use normal replica set management operations to handle (eg. add a new member, remove another member, etc).
|
Thank you. this has been merged. |
mongo-cr-bot
pushed a commit
that referenced
this pull request
Feb 8, 2023
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.
The idea of having logical DNS names for the config servers only applies the old-style triplet of config servers. The rationale for it is being able to redirect the logical DNS name mapping to another host, in order to "swap out" one of the 3 config servers. However, in the context of config servers as replsets, this is bad advice - any situation where you would "swap out" an old-style config server, with CSRS you should instead just use normal replica set management operations to handle (eg. add a new member, remove another member, etc).