-
Type:
New Feature
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
Fully Compatible
-
Sharding 2021-03-08, Sharding 2021-03-22, Sharding 2021-04-05, Sharding 2021-04-19
-
0
-
2
Should return error if the specified resharding operation does not exist or has completed already.
Should enter the critical section of the resharding operation if not already reached.
Should durably record decision to commit the resharding operation if not already done.
The commit flow is already implemented for resharding. This ticket is about introducing a new promise/future pair that the ReshardingCoordianator waits on and is fulfilled by the commitReshardCollection command.
We should consider adding a server parameter to preserve the existing "reshardin commits as quickly as possible" style of behavior to avoid impacting existing tests.
- depends on
-
-
- Closed
-
- is depended on by
-
-
- Closed
-
-
SERVER-56660 Remove need for reshardingCoordinatorCanEnterCriticalImplicitly failpoint from ReshardingTest fixture
-
- Closed
-
- related to
-
-
- Closed
-