[SERVER-25487] Initial sync should fail and restart if it receives renameCollection op to apply Created: 08/Aug/16  Updated: 06/Dec/22  Resolved: 29/Aug/16

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

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

Issue Links:
Depends
depends on SERVER-25332 Initial sync bootstrap needs to handl... Closed
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Operating System: ALL
Participants:

 Description   

If a renameCollection occurs during initial sync, the new collection may not be copied. The ideal fix would be to drop the original collection and re-clone the new collection. A quicker fix would be to just have the applier fail and cause initial sync to restart.



 Comments   
Comment by Eric Milkie [ 29/Aug/16 ]

Work will be covered in SERVER-25332

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