[SERVER-27357] Recreating collection with different collation during collection cloning phase can causes initial sync attempt to fail Created: 09/Dec/16  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: Replication
Affects Version/s: 3.4.0
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Robert Guo (Inactive) Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: initialSync
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-33946 Decrease number of initial sync attem... Blocked
Related
is related to SERVER-27122 Restart initial sync for known index ... Backlog
Assigned Teams:
Replication
Participants:
Linked BF Score: 0

 Description   

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.


Generated at Thu Feb 08 04:14:56 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.