[SERVER-25332] Initial sync bootstrap needs to handle collection metadata changes idempotently Created: 29/Jul/16  Updated: 14/Aug/17  Resolved: 14/Nov/16

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

Type: Bug Priority: Major - P3
Reporter: Eric Milkie Assignee: Siyuan Zhou
Resolution: Duplicate Votes: 0
Labels: Idempotency
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-26097 Create unittests for initial sync ide... Closed
depends on SERVER-26887 Idempotency of createCollection with ... Closed
depends on SERVER-26118 CollMod 'c' op: ignore metadata error... Closed
is depended on by SERVER-25040 Initial syncing node maintains tmp co... Closed
is depended on by SERVER-25057 Initial sync fails on 2d index build Closed
is depended on by SERVER-25487 Initial sync should fail and restart ... Closed
Duplicate
duplicates SERVER-26202 Relax index constraints in oplog appl... Closed
Related
related to SERVER-23932 Get collection info ASAP after listDa... Closed
related to SERVER-25403 DataReplicator initial sync should be... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2016-09-19, Repl 2016-10-10, Repl 2016-11-21
Participants:
Linked BF Score: 0

 Description   

During an initial sync, due to the way the collection catalogs are gleaned from the sync source, it is difficult to always accurately reflect the collection catalog at the time a given op was generated on the primary, at op application time.
Therefore, we must take extra steps to handle possible errors generated from certain ops that depend on accurate collection metadata. Some examples include collMod, createIndex, dropIndex, and createCollection.
For certain errors, we must ignore the error and subsequently ensure that another specific metadata operation is seen in the oplog stream before reaching minValid.



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

All the work was done on the linked server tickets, so closing this ticket as a dupe. Leave 3.2 required in fixed version to reminder us the backport.

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