[SERVER-33248] Allow choosing a sync source that we are up to date with if it has a higher lastOpCommitted Created: 09/Feb/18  Updated: 29/Oct/23  Resolved: 22/Aug/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.0.2, 4.1.3

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Related
related to SERVER-34855 Blacklist restart_catalog.js from cau... Closed
related to SERVER-39367 lastOpCommitted being reset on restar... Closed
related to SERVER-40193 Do not propagate commit point through... Closed
related to SERVER-40194 Revert SERVER-33248 on 4.0 Closed
is related to SERVER-39497 Revert SERVER-33248 Closed
is related to SERVER-32166 Do not clear sync source when going f... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.0
Sprint: Repl 2018-08-13, Repl 2018-08-27
Participants:
Linked BF Score: 68

 Description   

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.



 Comments   
Comment by Githook User [ 22/Mar/19 ]

Author:

{'email': 'tess.avitabile@mongodb.com', 'name': 'Tess Avitabile', 'username': 'tessavitabile'}

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

This reverts commit 5df9e94b0c4840680d1d17fcf2f04412cf6d70cf.
Branch: v4.0
https://github.com/mongodb/mongo/commit/3038797f87b9e355ff5151777b8474e57adb419c

Comment by Githook User [ 27/Feb/19 ]

Author:

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

Message: SERVER-39367 Advance commit point when it has the same term as the last applied

Comment by Githook User [ 22/Aug/18 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

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

(cherry picked from commit f5e7c8f3e81fe0cd34d4952ed2b547f3c29e06a4)
Branch: v4.0
https://github.com/mongodb/mongo/commit/5df9e94b0c4840680d1d17fcf2f04412cf6d70cf

Comment by Githook User [ 22/Aug/18 ]

Author:

{'name': 'Tess Avitabile', 'email': 'tess.avitabile@mongodb.com', 'username': 'tessavitabile'}

Message: SERVER-33248 Allow choosing a sync source that we are up to date with if it has a higher lastOpCommitted
Branch: master
https://github.com/mongodb/mongo/commit/f5e7c8f3e81fe0cd34d4952ed2b547f3c29e06a4

Comment by Spencer Brody (Inactive) [ 13/Feb/18 ]

This is more likely to be a problem in our tests than in actual production environments, where writes should be always happening (at least because of the no-op writer). So putting this onto the backlog. If it continues to cause issues for our testing we can do it, but otherwise we'll leave it alone.

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