Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Done
Priority: Major - P3
Fix Version/s: 3.2.12, 3.3.15
Affects Version/s: None
Component/s: Replication
Labels:
- Idempotency

Backwards Compatibility:
Fully Compatible
Backport Requested:

v3.2
Sprint:
Repl 2016-10-10
Case:
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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.

is duplicated by

SERVER-25040 Initial syncing node maintains tmp collection from map reduce when primary has renamed it

Closed

is related to

SERVER-4941 collection rename may not replicate / clone properly during initial sync

Closed

SERVER-29772 Provide option to 3.2 and 3.4 to allow initial sync to complete even when it encounters renameCollection entries

Closed

Assignee:: Siyuan Zhou
Reporter:: Crystal Horn (Inactive)
Participants:: Crystal Horn, Githook User, Siyuan Zhou
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Sep 14 2016 09:20:56 PM UTC
Updated:: Apr 29 2020 10:41:38 AM UTC
Resolved:: Sep 26 2016 11:02:34 PM UTC
Confidence Status Last Update:: 22/Sep/16 8:05 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates