[SERVER-46522] Config oplog commitment wait must retrieve optime under replication mutex Created: 02/Mar/20  Updated: 29/Oct/23  Resolved: 04/Mar/20

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.4.0-rc0

Type: Bug Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: Pavithra Vetriselvan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-45087 Check Oplog Commitment condition on r... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.4
Sprint: Repl 2020-03-09
Participants:

 Description   

When we retrieve the configOplogCommitmentOpTime here, we do not hold the ReplicationCoordinator mutex. We must acquire the mutex to call into TopologyCoordinator safely.



 Comments   
Comment by Githook User [ 04/Mar/20 ]

Author:

{'username': 'pvselvan', 'name': 'Pavi Vetriselvan', 'email': 'pvselvan@umich.edu'}

Message: SERVER-46473 oplog commitment check should only include voting nodes

SERVER-46522 config oplog commitment should retrieve optime under repl mutex
Branch: master
https://github.com/mongodb/mongo/commit/859b127ed3f86a180010be87cb1b9ccf81db9845

Generated at Thu Feb 08 05:11:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.