[SERVER-26203] CRUD Ops: All other errors: restart initial sync Created: 20/Sep/16  Updated: 05/Apr/17  Resolved: 01/Nov/16

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

Type: Task Priority: Major - P3
Reporter: Crystal Horn Assignee: Siyuan Zhou
Resolution: Done Votes: 0
Labels: Idempotency
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2016-10-10, Repl 2016-11-21
Participants:

 Description   

We don't refetch documents from source because of failures of oplog application. Instead, we make sure the insert/update/delete and other index related operations never fail due to index constraints in SERVER-26202. If unexpected failures happen, e.g. DocumentTooLarge(17419), we restart the initial sync. This design is because idempotency issues may also come from rollback and unclean shutdown, in the latter cases a sync source may not be available.



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

milkie, closing this ticket as Works as Designed because the restart logic is already there.

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