-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Sharding
-
Fully Compatible
-
v4.2
-
11
In this test we shard a collection through one router and expect another router to know that the collection is sharded. However, the second router can refresh its cache from a config server secondary, so if the config server has not replicated that the collection is sharded, the second router may refresh and think that the collection is unsharded. We should fix all instances of this assumption in this test by adding awaitReplication after sharding a collection.