[SERVER-40851] CheckReplDBHashInBackground should retry running 'appendOplogNote' when it fails to acquire the global lock Created: 26/Apr/19  Updated: 29/Oct/23  Resolved: 29/Apr/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.1.11

Type: Bug Priority: Major - P3
Reporter: Gregory Wlodarek Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Storage NYC 2019-05-06
Participants:
Linked BF Score: 18

 Description   

'appendOplogNote' has a deadline of 1 millisecond to acquire the global lock, otherwise it will fail with the 'LockFailed' error. In this scenario we should retry the 'appendOplogNote' in the CheckReplDBHashInBackground again at a later time.



 Comments   
Comment by Githook User [ 29/Apr/19 ]

Author:

{'name': 'Gregory Wlodarek', 'username': 'GWlodarek', 'email': 'gregory.wlodarek@mongodb.com'}

Message: SERVER-40851 CheckReplDBHashInBackground should retry running 'appendOplogNote' when it fails to acquire the global lock
Branch: master
https://github.com/mongodb/mongo/commit/ec5e2eb804baf6afba8abdcf2e269803537419da

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