[SERVER-63822] Modify TicketHolder with a concurrent queue Created: 18/Feb/22  Updated: 29/Oct/23  Resolved: 07/Mar/22

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

Type: Task Priority: Major - P3
Reporter: Jordi Olivares Provencio 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
depends on SERVER-63821 Create generic concurrent locking queue Closed
is depended on by SERVER-63824 Integrate Flow Control tickets into w... Closed
Duplicate
duplicates SERVER-63823 Replace write tickets with concurrent... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2022-03-07, Execution Team 2022-03-21
Participants:

 Description   

Currently the TicketHolder works based on a semaphore shared across all ticket acquirers. This means that the acquirer will be decided by whichever scheduling policy the kernel is using.

With the work on SERVER-63821 we want to use a queue of ticket acquirers in order to control the scheduling policy ourselves.



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

Author:

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

Message: SERVER-63822 Change TicketHolder implementation to use a FIFO queueing system
Branch: master
https://github.com/mongodb/mongo/commit/a11589e27cd657c078cf576af5599caa3ec24a38

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