Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Duplicate
Priority: Major - P3
Fix Version/s: None
Affects Version/s: None
Component/s: Replication
Labels:
- former-quick-wins
- initialSync

Assigned Teams:

Replication
Sprint:
Repl 2018-06-18, Repl 2018-07-02
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

resync is broken and not being fixed, but we still do resyncs in replSetSyncFrom which is dangerous. A safer way and cleaner way to choose a sync source would be a server parameter that specifies a preferred sync source for initial sync.

duplicates

SERVER-44272 Resync data on replSetSyncFrom during initial sync

Closed

is duplicated by

SERVER-33208 Remove all code related to resync command

Closed

is related to

SERVER-28840 replSetSyncFrom causes InitialSyncer and ReplicationCoordinator to acquire each other's mutexes in opposite orders

Closed

SERVER-35372 replSetSyncFrom can cause deadlock between ReplicationCoordinator and InitialSyncer

Closed

SERVER-38731 Ability to specify sync source read preference in initial sync

Closed

related to

SERVER-44272 Resync data on replSetSyncFrom during initial sync

Closed

(1 related to)

Assignee:: [DO NOT USE] Backlog - Replication Team
Reporter:: Judah Schvimer
Participants:: [DO NOT USE] Backlog - Replication Team, Alyson Cabral, Judah Schvimer, Siyuan Zhou, Spencer Brody, Tess Avitabile
Votes:: 1 Vote for this issue
Watchers:: 13 Start watching this issue

Created:: Oct 10 2017 03:07:49 PM UTC
Updated:: Dec 06 2022 03:49:40 AM UTC
Resolved:: Dec 06 2019 08:09:01 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates