DOCS-306 adding in line to link with Chunk Migration and Create Chunk section #182
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
|
revise and resubmit as discussed in person |
| you will have to migrate chunks manually to distribute chunks | ||
| evenly across the shards. | ||
|
|
||
| - If the balancer in an active cluster cannot distribute chunks within | ||
| the balancing window, then you will have to migrate chunks manually. | ||
|
|
||
| See the :ref:`chunk migration <sharding-chunk-migration>` section to | ||
| understand the internal process of how :term:`chunks <chunk>` move | ||
| between :term:`shards <shard>`. |
There was a problem hiding this comment.
only cross reference terms the first time that they appear in a section.
|
Please revise and resubmit. |
mongo-cr-bot
pushed a commit
that referenced
this pull request
Dec 22, 2021
mongo-cr-bot
pushed a commit
that referenced
this pull request
Jan 5, 2022
* DOCSP-20165-fix-about-page (#182) * fake commit * DOCSP-20166 BACKPORT * fake commit * DOCSP-20165 BACKPORT
mongo-cr-bot
pushed a commit
that referenced
this pull request
Jan 5, 2022
* DOCSP-20165-fix-about-page (#182) * fake commit * DOCSP-20166 BACKPORT * fake commit * DOCSP-20165 BACKPORT
mongo-cr-bot
pushed a commit
that referenced
this pull request
Jan 5, 2022
* DOCSP-20165-fix-about-page (#182) * fake commit * DOCSP-20166 BACKPORT * fake commit * DOCSP-20165 BACKPORT
mongo-cr-bot
pushed a commit
that referenced
this pull request
Jan 5, 2022
* DOCSP-20165-fix-about-page (#182) * fake commit * DOCSP-20166 BACKPORT * fake commit * DOCSP-20165 BACKPORT
mongo-cr-bot
pushed a commit
that referenced
this pull request
Jan 5, 2022
* DOCSP-20165-fix-about-page (#182) * fake commit * DOCSP-20166 BACKPORT * fake commit * DOCSP-20165 BACKPORT
mongo-cr-bot
pushed a commit
that referenced
this pull request
Jan 10, 2022
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
May 22, 2025
* DOCS-16422 clarifying write blocking behavior * DOCS-16422 clarifying write blocking behavior * DOCS-16422 clarifying write blocking behavior * DOCS-16422 copy edits * DOCS-16422 copy edits * DOCS-16422 copy edits * DOCSP-16422 moving commit section and copy edits * DOCS-16422 fixing reference * DOCS-16422 active voice * DOCS-16422 fixing reference * DOCS-16422 copy edit
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
May 22, 2025
* DOCS-16422 clarifying write blocking behavior * DOCS-16422 clarifying write blocking behavior * DOCS-16422 clarifying write blocking behavior * DOCS-16422 copy edits * DOCS-16422 copy edits * DOCS-16422 copy edits * DOCSP-16422 moving commit section and copy edits * DOCS-16422 fixing reference * DOCS-16422 active voice * DOCS-16422 fixing reference * DOCS-16422 copy edit
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
May 22, 2025
* add note that restoreDbUsersAndRoles requires dumpDbUsersAndRoles * How about spelling words correctly?
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 2, 2025
* DOCSP-19378 Helper add reference * DOCSP-19378 Helper add reference
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 6, 2025
* DOCSP-45453 1.11 release notes * Testing fix for staging error * Revert "Testing fix for staging error" This reverts commit 0a1f3e5edfae9389903a494326f2c8e6df9dd787. * Adds no foreign key found bug fix * Updates features section to include most recent edits * Fix release date in release notes
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 24, 2025
DOCSP-44301-1.11-release-notes-removal
mongodb-server-docs-sync-bot bot
pushed a commit
that referenced
this pull request
Jun 26, 2025
* init * first draft * edits * formatting fix * review feedback * wording * add on-prem clarification
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.
No description provided.