Clarification of replica set sizes #859
Closed
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
|
Thanks for the catch! Could you please sign the MongoDB/10gen contributor agreement before we proceed with getting this merged into the docs: http://www.10gen.com/legal/contributor-agreement Cheers, |
|
surely =) |
|
merged! |
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 23, 2025
* DOCSP-46527 -- Add GitHub access requirement note * DOCSP-46527 -- copy review revision (cherry picked from commit 8ef53b8)
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 26, 2025
* first commit, to be continued * Interim commit, to be continued * removing the step about cd to directory, as not needed * Build issues * fixing build errors * Fixing warnings * warnings * Made changes to the updgrade commands * Changed the syntax for setting the namespace * First round of copy review, to be continued * Fixing the build * Finish including copy and tech review comments from the first round. Ready for a review by John W * One more change, ready for a review * Addressed a few more comments from Rodrigo * Halfway through the copy review, to be continued * Added copy review * Ready for a review * Restaging * Address comment from Rodrigo in steps-helm-master * Tech review * indentation * Remaining edits: removed 1.7.1 steps from upgrades, removed update crd steps from upgrades, removed step 2 from plan-considerations topic as not relevant. Ready for the tech review by Mircea
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 26, 2025
* first commit, to be continued * Interim commit, to be continued * removing the step about cd to directory, as not needed * Build issues * fixing build errors * Fixing warnings * warnings * Made changes to the updgrade commands * Changed the syntax for setting the namespace * First round of copy review, to be continued * Fixing the build * Finish including copy and tech review comments from the first round. Ready for a review by John W * One more change, ready for a review * Addressed a few more comments from Rodrigo * Halfway through the copy review, to be continued * Added copy review * Ready for a review * Restaging * Address comment from Rodrigo in steps-helm-master * Tech review * indentation * Remaining edits: removed 1.7.1 steps from upgrades, removed update crd steps from upgrades, removed step 2 from plan-considerations topic as not relevant. Ready for the tech review by Mircea
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jul 1, 2025
…t (858) (#859) # Backport This will backport the following commits from `master` to `v8.0`: - [(DOCSP-49806) Clarify misleading parameters description. (#858)](10gen/docs-ops-manager#858) <!--- Backport version: 9.6.1 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport)
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 line changed was a line I found misleading/a point of concern after being a mongo user for nearly 9 months. Since a two member replica set is an unusual configuration, most users reading the Deploy a Replica Set page are probably better served by indicating that most replica sets are three or more members.