[SERVER-58518] Report progress of collection defragmentation through balancerCollectionStatus command Created: 14/Jul/21 Updated: 29/Oct/23 Resolved: 25/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Simon Gratzer (Inactive) | Assignee: | Paolo Polato |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Sharding EMEA 2022-01-24, Sharding EMEA 2022-02-07 | ||||||||
| Participants: | |||||||||
| Description |
|
The new command created in 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. |
| Comments |
| Comment by Githook User [ 25/Jan/22 ] |
|
Author: {'name': 'Paolo Polato', 'email': 'paolo.polato@mongodb.com', 'username': 'ppolato'}Message: |
| Comment by Paolo Polato [ 17/Dec/21 ] |
|
Proposed content of the of the report:
To be addressed: behavior of the command on node step-down / initialisation scenarios. |