[
https://issues.apache.org/jira/browse/YUNIKORN-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chenya Zhang updated YUNIKORN-717:
----------------------------------
Description:
Defining "totalNodeActive" and "totalNodeFailed" to initialize scheduler
metrics is redundant in code.
* It can be combined into "nodeStatus"
* It can use a "prometheus.CounterVec" with different Prometheus labels
Defining "nodeSortingLatency", "appSortingLatency", and "queueSortingLatency"
to initialize scheduler metrics is redundant in code.
* It can be combined into "sortingLatency"
* It can use a "prometheus.CounterVec" with different Prometheus labels
was:
Defining "totalNodeActive" and "totalNodeFailed" to initialize scheduler
metrics is redundant in code.
* It can be combined into "nodeStatus"
* It can use a "prometheus.CounterVec" with different Prometheus labels
> Refactor YuniKorn core's scheduler metrics for node status
> ----------------------------------------------------------
>
> Key: YUNIKORN-717
> URL: https://issues.apache.org/jira/browse/YUNIKORN-717
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: core - common
> Reporter: Chenya Zhang
> Assignee: Alkaid Jiang
> Priority: Major
>
> Defining "totalNodeActive" and "totalNodeFailed" to initialize scheduler
> metrics is redundant in code.
> * It can be combined into "nodeStatus"
> * It can use a "prometheus.CounterVec" with different Prometheus labels
> Defining "nodeSortingLatency", "appSortingLatency", and "queueSortingLatency"
> to initialize scheduler metrics is redundant in code.
> * It can be combined into "sortingLatency"
> * It can use a "prometheus.CounterVec" with different Prometheus labels
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
