[SERVER-26117] renameCollection 'c' op should restart initial sync upon application Created: 14/Sep/16  Updated: 29/Apr/20  Resolved: 26/Sep/16

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

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

Issue Links:
Backports
Documented
is documented by DOCS-10763 Document that upgrading to 3.2.12 and... Closed
Duplicate
is duplicated by SERVER-25040 Initial syncing node maintains tmp co... Closed
Related
is related to SERVER-4941 collection rename may not replicate /... Closed
is related to SERVER-29772 Provide option to 3.2 and 3.4 to allo... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.2
Sprint: Repl 2016-10-10
Participants:
Case:

 Description   

This is to avoid the syncing node winding up with an incomplete set of data due to the inability of initial sync to properly handle renameCollection. See SERVER-4941 for more details.



 Comments   
Comment by Githook User [ 13/Jan/17 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'visualzhou@gmail.com'}

Message: SERVER-26117 renameCollection 'c' op should restart initial sync upon application
Branch: v3.2
https://github.com/mongodb/mongo/commit/5313582dae3fc0fe11d91dbbc3d2a8154de3b038

Comment by Githook User [ 26/Sep/16 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-26117 renameCollection 'c' op should restart initial sync upon application
Branch: master
https://github.com/mongodb/mongo/commit/7928661bfc0dcccc95256e0df6424b057d588eec

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