-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: 4.1.4
-
Component/s: Sharding
-
Fully Compatible
-
ALL
-
v4.0
-
Sharding 2018-12-17
When config server rollbacks data its ShardRegistry that is used for targeting gets out of sync. Instead, it should immediately call reload to avoid the inconsistent state.
- causes
-
SERVER-39498 ShardRegistry reload inside onReplicationRollback can get stuck
- Closed
- is related to
-
SERVER-32375 Config metadata commands should not use readConcern majority
- Closed
-
SERVER-33256 shardCollection gets DuplicateKeyError if it retries inserting to config.collections after failing to wait for writeConcern
- Closed