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