[SERVER-63821] Create generic concurrent locking queue Created: 18/Feb/22 Updated: 28/Feb/22 Resolved: 28/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jordi Olivares Provencio | Assignee: | Jordi Olivares Provencio |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Sprint: | Execution Team 2022-03-07 | ||||||||||||
| Participants: | |||||||||||||
| 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. |
| Comments |
| Comment by Jordi Olivares Provencio [ 28/Feb/22 ] |
|
Reusing the implementation in the codebase |