[SERVER-81318] The TimestampMonitor should be high priority and not take tickets Created: 21/Sep/23  Updated: 27/Nov/23  Resolved: 22/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.2.0-rc0, 7.0.3

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

Issue Links:
Backports
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v7.1, v7.0
Sprint: Execution NAMR Team 2023-10-02
Participants:
Linked BF Score: 40

 Description   

As of SERVER-79982, the TimestampMonitor is taking flow control tickets and storage engine tickets every iteration. Previously, it would only take tickets when dropping idents. Since this is an important background cleanup task, we should exempt it from taking tickets.

Nothing should be depending on the TimestampMonitor to free its resources, but being forced to take tickets could delay freeing up disk space longer than necessary.



 Comments   
Comment by Githook User [ 05/Oct/23 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-81318 Make TimestampMonitor high priority

(cherry picked from commit b05256eb0a1cfbca6584ecde00d602ff037f5444)
Branch: v7.0
https://github.com/mongodb/mongo/commit/89b25d10c2743bf237cb832ebeb3250b779f4500

Comment by Githook User [ 22/Sep/23 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-81318 Make TimestampMonitor high priority
Branch: master
https://github.com/mongodb/mongo/commit/b05256eb0a1cfbca6584ecde00d602ff037f5444

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