For example, in removeShard command it get trigger a ShardRegistry refresh, but it uses the same operation context to do a readConcern majority read, and this can cause some weird behavior because the command will think that shards exists, when in fact they no longer do.
- is duplicated by
-
SERVER-31414 The writes of _configsvrEnableSharding to config.databases do not use local write concern
- Closed
-
SERVER-33256 shardCollection gets DuplicateKeyError if it retries inserting to config.collections after failing to wait for writeConcern
- Closed
- is related to
-
SERVER-30559 Sharding tests which run under continuous stepdown must allow for lastVisibleOp to go backwards
- Closed
- related to
-
SERVER-37929 ShardRegistry in config servers can keep invalid entries after it rolls back until next reload
- Closed