-
Type: Improvement
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Sharding
-
Sharding EMEA 2021-12-27, Sharding EMEA 2022-01-10
-
0
ShardingTest has some restart functions – restartMongos, restartMongod, etc. – that additionally update ShardingTest._connections, but it doesn't have any restartReplicaSet functionality that would update ShardingTest._connections.
We need a new ShardingTest function that wraps around ReplSetTest.stopSet() and ReplSetTest.startSet() and updates ShardingTest._connections.
------------- motivation below ------------
checkUUIDsConsistentAcrossCluster uses ShardingTest._connections to get shard primary targeting information. It directly calls listCollection against what it thinks in the shard primary, here, but because key_rotation.js restarts a shard replica set directly, here, ShardingTest._connections probably isn't getting updated with the latest information.
- is depended on by
-
SERVER-31385 ShardingTest.prototype.checkUUIDsConsistentAcrossCluster not resilient to closed connections
- Closed
- is related to
-
SERVER-31668 checkUUIDsConsistentAcrossCluster must retry on NotMaster errors
- Closed
- related to
-
SERVER-31385 ShardingTest.prototype.checkUUIDsConsistentAcrossCluster not resilient to closed connections
- Closed
-
SERVER-31529 Add TestData.skipCheckingUUIDsConsistentAcrossCluster = true to key_rotation.js
- Closed