Disable balancer while indexes are inconsistent #1766
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
cursor.sort() contains a warning about the 32MB limit on non-indexed sorting, this adds the same warning to $orderby - which is the underlying operator that powers sort(). The warning is largely a copy+paste with superficial name replacements. Signed-off-by: kay <[email protected]>
Signed-off-by: kay <[email protected]>
A chunk migration can cause an index build, so we should advise to disable the balancer to avoid performance issues.
| :term:`shard`. Also ensure the balancer has been disabled for all | ||
| collections on which you'll be creating an new index. This will prevent | ||
| an automatic index build as chunks are migrated. The balancer should be | ||
| enabled after the indexes have been updated on all shards. |
There was a problem hiding this comment.
putting this fact here is pretty awkward, because the tutorial isn't about sharded clusters, and so this fact might be weird for users in a sharded cluster. Perhaps we can put this fact somewhere else and then cross reference it here?
|
It looks like this pull request/branch is in a weird state. Could you rebase to make it seem a bit more coherent. |
|
Feel free to open this as a DOCS ticket and we can figure out the best place for this bit of information if you like. |
|
note: backport to 2.4 |
|
Bulk closing stale pull requests. |
mongo-cr-bot
pushed a commit
that referenced
this pull request
Sep 2, 2022
* DOCS-15590-refineshardkey-updates * DOCS-15590-refineshardkey-updates * DOCS-15590-refineshardkey-updates Co-authored-by: jason-price-mongodb <[email protected]> Co-authored-by: jason-price-mongodb <[email protected]>
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.
A chunk migration can cause an index build, so we should advise to disable the balancer to avoid performance issues.