Update source/tutorial/deploy-replica-set.txt #509
Merged
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
Fixed the requirements section to agree with the docs here: http://docs.mongodb.org/manual/core/replication/ The requirement for a set is two or more, but the tutorial describes three, and it led to some confusion in the community: http://serverfault.com/questions/462780/does-a-mongodb-replica-set-require-at-least-2-or-3-members
Really fixed the Requirements section to betterreflect the intent and agree with docs elsewhere.
mongo-cr-bot
pushed a commit
that referenced
this pull request
Feb 3, 2022
Co-authored-by: Sarah Olson <[email protected]> Co-authored-by: Sarah Olson <[email protected]>
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
May 22, 2025
* DOCSP-43406-write-blocking-limitation-clarification * DOCSP-43406 fixing ref' * DOCSP-43406 fixing ref * DOCSP-43406 fixing ref * DOCSP-43406 copy edits * DOCSP-43406 tech edit (cherry picked from commit cd47f51)
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 26, 2025
…ions from 1.0 -1.5.x inclusive from the compatibility tables (#509) * (DOCSP-14341) Added MEKO 1.9.x to the EOL table * Also updating the compatibility tables: removing all versions up to 1.6.0, and adding 1.9.0
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 26, 2025
…ions from 1.0 -1.5.x inclusive from the compatibility tables (#509) * (DOCSP-14341) Added MEKO 1.9.x to the EOL table * Also updating the compatibility tables: removing all versions up to 1.6.0, and adding 1.9.0
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.
Fixed the requirements section to agree with the docs here:
http://docs.mongodb.org/manual/core/replication/
The requirement for a set is one or more, with the usual deployment of 2 or more etc.
The tutorial describes three, hence the language and it led to some confusion in the community:
http://serverfault.com/questions/462780/does-a-mongodb-replica-set-require-at-least-2-or-3-members