-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
When there are multiple job acquisitions querying the job table (e.g. in a cluster), they may select the same jobs for acquisition. For each job, only one of them can win and lock it. That means in practice (and as observed in benchmarks), the job acquisition often acquires + locks less jobs for execution than it could do.
This problem may become even more evident when we enforce an ordering on jobs as request in CAM-1214
This is the controller panel for Smart Panels app
Improve Job Acquisition Hit Rate
-
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
When there are multiple job acquisitions querying the job table (e.g. in a cluster), they may select the same jobs for acquisition. For each job, only one of them can win and lock it. That means in practice (and as observed in benchmarks), the job acquisition often acquires + locks less jobs for execution than it could do.
This problem may become even more evident when we enforce an ordering on jobs as request in CAM-1214
This is the controller panel for Smart Panels app
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
CAM-4023 Spike: Benchmark job acquisition in cluster
-
- Closed
-
-
-
- Closed
-
-
Thorben Lindhauer
-
- Votes:
-
0 Vote for this issue
- Watchers:
-
2 Start watching this issue
- Created:
- Updated:
- Resolved: