[SERVER-77688] Consider bypassing ticket acquisition for locks in hot sharding codepaths Created: 01/Jun/23 Updated: 26/Oct/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Backlog - Catalog and Routing |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | oldshardingemea, shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Catalog and Routing
|
| Participants: | |
| Story Points: | 3 |
| Description |
|
Some locks acquired/release by the internal sharding machinery are "hot" because user operations may be impacted when the acquisition/release is delayed because of tickets unavailability. An example of sensible path is the acquisition/release of the critical section. Purpose of this task is to identify such hot paths and consider using ScopedAdmissionPriorityForLock in order to bypass ticketing, similarly to what has been committed under |