Details
-
Task
-
Resolution: Won't Do
-
Major - P3
-
None
-
None
-
None
-
None
-
Execution Team 2022-03-07
Description
In order to sustain the efforts of the project, we want to develop our own concurrent queue data structure. We should first verify though that it's not something already made in the codebase, in which case we should reuse it for our needs.
Ideally this should be an interface for the queue with various supporting implementations in case we want to explore other priorization policies down the line.
This should encompass also writing tests in order to verify its correctness.
Something to take into account is that this isn't a traditional queue as the act of submitting something to it should block the caller until the lock is granted.
Attachments
Issue Links
- depends on
-
SERVER-63956 Separate Interface and implementation of the TicketHolder
-
- Closed
-
- is depended on by
-
SERVER-63822 Modify TicketHolder with a concurrent queue
-
- Closed
-