-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Labels:None
A new cause of imbalance (named "defragmentingChunks") can now be reported to the user through the balancerCollectionStatus(namespace) command.
This happens when the queried namespace is currently going through the chunk defragmentation process (which is triggered by the user through the ConfigureCollectionBalancing() command).
In such case, the returned message also includes extra information on the current status of the defragmentation. An example follows:
{"balancerCompliant":false,"firstComplianceViolation":"defragmentingChunks","details":{"currentPhase":"moveAndMergeChunks","progress":{"remainingChunksToProcess":1}}
Description of Linked Ticket
The new command created in SERVER-58270 can put the collection in a “defragmentation” mode whereby the balancer will merge and move chunks around in order to yield a number of chunks approximately equal to the TotalDataSize/DefaultChunkSize evenly distributed across the appropriate shards.
The defragmentation is a one-time operation (which potentially may take a long time) and after that the collection will leave the “defragmentation” mode.
Its progress will be able to be monitored from the return of the balancerCollectionStatus command.
- documents
-
-
- Closed
-