It can happen that due to the majority write need when getting metadata from CSRS, if replication is off due to a stepdown, findAndModify gets a StaleConfig error. This behaviour makes sense, so the test should be fixed.
- depends on
-
SERVER-78115 Shard primaries must commit a majority write before using new routing information from the config server
- Closed