[SERVER-75493] OplogNote waits only 1 millisecond to acquire GlobalLock Created: 30/Mar/23  Updated: 11/Jul/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Haley Connelly Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-75499 Perform no-op oplog entry write for a... Closed
Assigned Teams:
Replication
Operating System: ALL
Participants:
Linked BF Score: 148

 Description   

We should investigate the ramifications of increasing this timeout / removing the timeout. We've seen several test failures recently as a result of this timeout. 



 Comments   
Comment by Gregory Noma [ 30/Mar/23 ]

We're doing SERVER-75499 in order to prevent spurious timeouts due to ticket acquisition here, but it still may be valuable to investigate whether the timeout is necessary. If we're able to remove the timeout, we also may be able to revert back to normal priority ticket acquisition.

Comment by Haley Connelly [ 30/Mar/23 ]

We believe the timeout has been exacerbated as a result of turning on execution control in SERVER-52207 which makes it more likely tickets are exhausted and OplogNote will need to wait to acquire the GlobalLock

 

Generated at Thu Feb 08 06:30:19 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.