Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
4.1.4
-
Fully Compatible
-
ALL
-
v4.0
-
Sharding 2018-12-17
Description
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.
Attachments
Issue Links
- 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
-