Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 4.0.2, 4.1.3
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Backport Requested:

v4.0
Sprint:
Repl 2018-08-13, Repl 2018-08-27
Linked BF Score:
68
Confidence Status:
None
Work Order:
3

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

If you lose your sync source once you're up to date but before you update your lastOpCommitted, it can prevent secondary majority reads from progressing.

This definitely needs to be investigated for how to do this correctly and safely.

is related to

SERVER-39497 Revert SERVER-33248

Closed

SERVER-32166 Do not clear sync source when going from RECOVERING to SECONDARY

Closed

related to

SERVER-34855 Blacklist restart_catalog.js from causal consistency suites

Closed

SERVER-39367 lastOpCommitted being reset on restart can cause sync source cycle

Closed

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

Closed

SERVER-40194 Revert SERVER-33248 on 4.0

Closed

(1 related to)

Assignee:: Tess Avitabile (Inactive)
Reporter:: Judah Schvimer
Participants:: Githook User, Judah Schvimer, Spencer Brody, Tess Avitabile
Votes:: 3 Vote for this issue
Watchers:: 16 Start watching this issue

Created:: Feb 09 2018 09:11:05 PM UTC
Updated:: Oct 29 2023 10:34:52 PM UTC
Resolved:: Aug 22 2018 02:43:16 PM UTC
Confidence Status Last Update:: 09/Aug/18 1:19 PM

Details

Description

Attachments

Issue Links

Activity

People

Dates