-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.6.2, 3.7.1
-
Component/s: Sharding
-
ALL
-
v3.6
-
Sharding 2018-11-19
-
5
This write done by _configsvrShardCollection to write the collection entry to the sharding catalog uses majority writeConcern and the kIdempotent RetryPolicy.
If it fails to wait for writeConcern, it will be retried because of the kIdempotent policy, and the retry will see DuplicateKeyError because the document has already been written locally.
- duplicates
-
SERVER-32375 Config metadata commands should not use readConcern majority
- Closed
- related to
-
SERVER-37929 ShardRegistry in config servers can keep invalid entries after it rolls back until next reload
- Closed