[SERVER-66152] Implement centralized ticket acquisition that allows op prioritisation Created: 03/May/22 Updated: 29/Oct/23 Resolved: 30/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Improvement | 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 | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2022-05-16, Execution Team 2022-05-30, Execution Team 2022-06-13, Execution Team 2022-06-27, Execution Team 2022-07-11 |
| Participants: |
| Description |
|
As part of the Execution Control initiative we want to explore having a centralized TicketHolder implementation that takes into account the type of operations we are performing and lets us apply a dequeueing policy. Initially we want to use a user-settable knob of the prioritisation of reads vs writes. |
| Comments |
| Comment by Githook User [ 30/Jun/22 ] |
|
Author: {'name': 'Jordi Olivares Provencio', 'email': 'jordi.olivares-provencio@mongodb.com', 'username': 'jordiolivares'}Message: |