-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
v5.1, v5.0
-
Sharding 2021-07-12, Sharding 2021-07-26, Sharding 2021-08-09, Sharding 2021-10-18, Sharding 2021-11-01, Sharding 2021-11-15
-
2
- Resharding should run while having config and data nodes stepdown & stepup periodically.
- This will require the resharding operation to run for a long enough time to accommodate multiple elections.
- depends on
-
SERVER-60775 PrimaryOnlyService won't wait for prior Instance on step up if InstanceID had completed on an interceding primary already (ABA problem)
- Backlog
-
SERVER-58407 Resharding components do not retry on FailedToSatisfyReadPreference when targeting remote shard, leading to server crash
- Closed
-
SERVER-60774 Resharding may apply through reshardFinalOp without transitioning to strict consistency, stalling write operations on collection being resharded until critical section times out
- Closed
-
SERVER-60858 _configsvrReshardCollection command which joins existing ReshardingCoordinator may miss being interrupted on stepdown
- Closed
-
SERVER-60859 ReshardingCoordinator waits on _canEnterCritical future without cancellation, potentially preventing config server primary step-up from ever completing
- Closed
-
SERVER-61052 Resharding Donor & Recipient's Coordinator Doc Updates Can Time Out Waiting for Replication on Coordinator Doc, Leading to Fatal Assertion
- Closed
- related to
-
SERVER-60860 ReshardingCollectionCloner uses primary read preference when nearest was intended
- Closed