-
Type:
Bug
-
Resolution: Done
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Cluster Scalability
-
ALL
-
ClusterScalability 31Aug-14Sep
-
200
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The afterEach hook's ShardingTest.stop({skipValidation: true}) call still unconditionally runs checkMetadataConsistency(), which is not gated by skipValidation. This test deliberately stops/restarts the replica set and mongos mid-test, so by the time checkMetadataConsistency opens its own fresh connection to mongos, the process can already have exited, causing a spurious connection-refused failure in cleanup rather than a real test failure.
- related to
-
SERVER-134075 Potentially make stop manually added shard after calling ShardingTest.stop in add_shard_refurbish.js
-
- Closed
-