-
Type: Improvement
-
Resolution: Won't Do
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
None
-
Sharding EMEA
-
Sharding 2017-12-04, Sharding 2017-12-18
-
15
The UUID check is failing because slow machines can cause unexpected shard primary step downs, and the UUID check does listCollections directly against the shard, which only runs on a primary and returns NotMaster if the expected primary is no longer primary.
SERVER-31583 and SERVER-31385 are related checkUUIDsConsistentAcrossCluster problems.
- is related to
-
SERVER-31643 Make drop collection in concurrency workloads retry LockBusy errors
- Closed
- related to
-
SERVER-31385 ShardingTest.prototype.checkUUIDsConsistentAcrossCluster not resilient to closed connections
- Closed
-
SERVER-31583 Update ShardingTest._connections when a replica set is restarted
- Closed