Mit Desai created YUNIKORN-3120:
-----------------------------------
Summary: Enhance Scheduling Latency Metrics with Allocation State
Labels
Key: YUNIKORN-3120
URL: https://issues.apache.org/jira/browse/YUNIKORN-3120
Project: Apache YuniKorn
Issue Type: Improvement
Components: core - scheduler
Reporter: Mit Desai
Assignee: Mit Desai
h2. Summary
Enhance the existing scheduling latency metrics by adding state labels to
distinguish between scheduling cycles that result in successful pod allocation
versus cycles that don't find suitable allocations. This improvement will
significantly enhance debugging capabilities for scheduling performance issues.
h2. Background
Currently, YuniKorn's {{yunikorn_scheduler_scheduling_latency_milliseconds}}
metric aggregates all scheduling cycles together, making it difficult to
distinguish between:
# {*}Allocation cycles{*}: Cycles where the scheduler successfully finds and
allocates resources for pending applications
# {*}Non-allocation cycles{*}: Cycles where the scheduler runs but cannot find
suitable allocations due to resource constraints, policy restrictions, or other
factors
This lack of distinction makes it challenging to debug scheduling latency
issues, as operators cannot easily identify whether high latency is due to
complex allocation decisions or repeated failed allocation attempts.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: dev-h...@yunikorn.apache.org
