-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding, Testing Infrastructure
-
None
-
Sharding NYC
-
Fully Compatible
-
v6.0, v5.0
-
Sharding NYC 2023-02-20
-
49
To avoid hanging or crashing the mongo shell process, the ReshardingTest fixture goes through some lengths to interrupt the reshardCollection command on mongos and join the background thread in the mongo shell which was running the reshardCollection command. However, after the changes from 0d5fd57 as part of SERVER-61985, the reshardCollection command may be blocked on the reshardingPauseCoordinatorBeforeCompletion failpoint without having waited on the interceding reshardingPauseCoordinatorBeforeBlockingWrites and reshardingPauseCoordinatorBeforeDecisionPersisted failpoints. This means the _commandDoneSignal won't be decremented to break the ReshardingTest fixture out of _waitForFailPoint(). Instead the mongo shell reports a scenario where the reshardCollection will have definitively failed as an assert.soon() failpoint of not reaching the expected failpoint within the allotted time.
- is related to
-
SERVER-61985 resharding_coordinator_recovers_abort_decision.js may report resharding operation as succeeding due to primary shard retrying _configsvrReshardCollection and running a second resharding operation
- Closed
-
SERVER-65201 De-emphasize errors which are ignored by the ReshardingTest fixture when another error has already occurred
- Closed