Loading...

XML

Word

Printable

JSON

Details

Type: Bug
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.1.9
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Operating System:
ALL
Backport Requested:

v4.0
Sprint:
Repl 2019-03-11
Linked BF Score:
15

Description

Consider two nodes in a set, nodes A and B. Node A restarts (resetting its lastOpCommitted to 0) and is ahead of node B. Node B syncs from A. A has no lastOpCommitted so A chooses to sync from B which has a non-zero lastOpCommitted, even though B is already syncing from A.

Attachments

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List
  - Download All

sync_source_cycle.js
4 kB
Feb 05 2019 04:03:02 AM UTC

Issue Links

is duplicated by

SERVER-39497 Revert SERVER-33248

Closed

is related to

SERVER-27123 Only update commit point via spanning tree

Closed

SERVER-39353 disable chaining in rollback_test.js

Closed

SERVER-39497 Revert SERVER-33248

Closed

SERVER-39626 Majority committed oplog entries may be rolled back on minority nodes

Closed

SERVER-39831 Never update commit point beyond last applied if learned from sync source

Closed

SERVER-33248 Allow choosing a sync source that we are up to date with if it has a higher lastOpCommitted

Closed

related to

SERVER-40193 Do not propagate commit point through heartbeats when FCV=4.0

Closed

SERVER-40194 Revert SERVER-33248 on 4.0

Closed

(2 is related to, 2 related to)

Activity

People

Assignee:: Siyuan Zhou

Reporter:: Judah Schvimer

Participants:: Githook User, Judah Schvimer, Siyuan Zhou, Tess Avitabile, William Schultz

Votes:: 0 Vote for this issue

Watchers:: 15 Start watching this issue

Dates

Created:: Feb 04 2019 07:06:39 PM UTC

Updated:: Oct 29 2023 10:24:26 PM UTC

Resolved:: Feb 27 2019 01:53:03 AM UTC