-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding, Testing Infrastructure
-
Fully Compatible
-
v5.1, v5.0
-
Sharding 2021-08-09, Sharding 2021-09-06, Sharding 2021-09-20, Sharding 2021-10-04, Sharding 2021-10-18
-
1
Probably limit to only a new variation of the "shuffle" (--numDonors 3 --numRecipients 3 --inPlace no) form.
- depends on
-
SERVER-59023 Resharding can fail with NamespaceNotSharded following a primary failover on a recipient shard
- Closed
-
SERVER-59114 ReshardingOplogFetcher stops fetching new oplog entries if remote donor shard responds with Interruption exception
- Closed
-
SERVER-59721 Node may become unable to sync from other members after performing rollback to stable timestamp
- Closed
-
SERVER-59775 ReshardingDonorOplogIterator triggers an fassert() when it continues to run in member state SECONDARY following a stepdown
- Closed
-
SERVER-59811 ReshardingOplogFetcher can see the postBatchResumeToken move backwards in time when switching sync sources, stalling the resharding operation
- Closed
-
SERVER-59812 ReshardingMetrics::onStepDown() is called while data replication components are still running, leading to an invariant failure
- Closed
-
SERVER-59927 Resharding's RecipientStateMachine::_restoreMetrics() doesn't retry on transient errors, leading to fassert() on stepdown
- Closed
-
SERVER-59057 Do not enforce fast count in validate command for config.transactions collection
- Closed
-
SERVER-59693 ReshardingTest fixture must accommodate nodes going into ROLLBACK while attempting to run replSetStepUp
- Closed
-
SERVER-59923 Retry reshardCollection command from background thread in ReshardingTest fixture
- Closed
-
SERVER-57667 Improve processing speed for resharding's collection cloning pipeline
- Closed