-
Type: Bug
-
Resolution: Gone away
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Sharding 2020-03-23, Sharding 2020-04-06
-
0
In view_rewrite.js, the test enables sharding on a database and then shards a collection. Sharding a collection requires the database have sharding enabled. However, this can fail under unusual circumstances when a stepdown occurs between enabling sharding on the database and sharding the collection; the write to the config server indicating that the database has sharding enabled may no longer be visible (though it is guaranteed to eventually become visible).
- related to
-
SERVER-30615 _configsvrShardCollection can retry upsert after getting writeConcern timeout and result in duplicate key error
- Closed
-
SERVER-32375 Config metadata commands should not use readConcern majority
- Closed