[SERVER-26771] Idempotency in cloning phase of initial sync Created: 25/Oct/16  Updated: 06/Dec/22  Resolved: 03/Nov/16

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

Type: Bug Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Backlog - Replication Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-26202 Relax index constraints in oplog appl... Closed
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

Since we copy the data from different snapshots and start building indexes before cloning data. The index spec may be inconsistent with the copied data, causing idempotency issues.

Creat geo index
--- start clone, get the geo index ---
Drop the geo index
Insert an invalid geo document
--- copy the data, triggering geo parsing errors ----

Relaxing index constraints in data cloning is one possible solution.



 Comments   
Comment by Siyuan Zhou [ 03/Nov/16 ]

Closing as a dup because index building, doc insert, update and delete are all covered by SERVER-26202.

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