[SERVER-61836] The TimestampMonitor must ignore killOp interruptions and retry/continue Created: 01/Dec/21  Updated: 29/Oct/23  Resolved: 28/Jan/22

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

Type: Bug Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Jordi Olivares Provencio
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: Execution Team 2022-02-07
Participants:
Linked BF Score: 15

 Description   

The fuzzer decided to killOp the TimestampMonitor. We need to make the internal thread safe against killOp: retry on Interrupted errors.



 Comments   
Comment by Githook User [ 28/Jan/22 ]

Author:

{'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}

Message: SERVER-61836 Add resiliency against killOp in TimestampMonitor
Branch: master
https://github.com/mongodb/mongo/commit/fa5e93cc4211bf8489a1795a735351fb3c28a369

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