-
Type: New Feature
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Fully Compatible
-
Sharding 2021-03-08, Sharding 2021-03-22, Sharding 2021-04-05, Sharding 2021-04-19, Sharding 2021-05-03
-
134
-
2
Add a remainingReshardingOperationTimeMillisThreshold server parameter to control when the coordinator should engage the critical section (default value of 2s)
Should contact each recipient to gather statistics.
Should continuously monitor while a ReshardingCoordinator service instance exists.
Should stop monitoring when the coordinator instance exits or we reach the critical section of the coordinator.
Should provide ability to determine if all recipients report they can finish within the remainingReshardingOperationTimeMillisThreshold.
Engage critical section once all recipients report they can finish within remainingOperationTimeMillisThreshold.
- causes
-
SERVER-56215 Ensure current client is set in CoordinatorCommitMonitor unit-tests
- Closed
- has to be done before
-
SERVER-55683 Remove waiting for minimum duration from the resharding coordinator
- Closed
- is depended on by
-
SERVER-55684 Remove resharding's RecipientStateEnum::kSteadyState state
- Closed
-
SERVER-56660 Remove need for reshardingCoordinatorCanEnterCriticalImplicitly failpoint from ReshardingTest fixture
- Closed
- is related to
-
SERVER-53919 Add a remainingReshardingOperationTimeMillisThreshold server parameter to control when the coordinator should engage the critical section
- Closed
-
SERVER-53921 Engage critical section once all recipients report they can finish within remainingOperationTimeMillisThreshold
- Closed