-
Type: Bug
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: 3.4.0
-
Component/s: Replication
-
Replication
-
0
If a collection is dropped and recreated with different collation options between when the DatabaseCloner calls listCollections and when its CollectionCloner calls listIndexes, the initial sync attempt will fail.
The failure happens during creation of the _id index, where IndexCatalog::_isSpecOk can throw a number of different collation related errors if the collation specified in the collection options is different to that of the _id index spec.
- is depended on by
-
SERVER-33946 Decrease number of initial sync attempts in tests to 1
- Blocked
- is related to
-
SERVER-27122 Restart initial sync for known index idempotency errors; fail for unknown ones.
- Backlog