range_deleter_interacts_correctly_with_refine_shard_key.js steps up a new primary and then creates an index through a mongos right after. If the router's RSM is not using the streamable protocol, it may have a stale view of the primary and the createIndexes will target the old primary and fail with NotMaster. To support the non-streamable protocols, the test should wait for the router's RSM to detect the new primary before creating the index.
- is related to
-
SERVER-48198 Migration recovery may recover incorrect decision after shard key refine
- Closed