[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: |
|
||||||||||||||||
| 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. |