[SERVER-59966] Implement an initialisation routine in BalancerCommandsScheduler to support ConfigServer step down / crash events Created: 15/Sep/21 Updated: 29/Oct/23 Resolved: 05/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Paolo Polato | 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 2021-10-04, Sharding EMEA 2021-10-18 | ||||||||
| Participants: | |||||||||
| Description |
|
The collection chunks defragmentation algorithm info involves the submission of moveChunk commands from the ConfigServer through BalancerCommandsScheduler. The involved shards may require tens of seconds to complete such operation, during which an election of a new ConfigServer primary may occur: the new primary will have to resume the defragmentation algorithm from a stable state - meaning that no new commands may be issued as long as all the moveChunk operations launched by its predecessor have completed. Such logic needs to be implemented within BalancerCommandsScheduler relying on the persisted information about previously issued moveChunk operations (see |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |