[
https://issues.apache.org/jira/browse/YUNIKORN-2530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Condit resolved YUNIKORN-2530.
------------------------------------
Fix Version/s: 1.6.0
Resolution: Fixed
Merged all PRs to master.
> Remove unnecessary ready flag on node
> -------------------------------------
>
> Key: YUNIKORN-2530
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2530
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: core - scheduler, scheduler-interface, shim - kubernetes
> Reporter: Craig Condit
> Assignee: Craig Condit
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.6.0
>
>
> YuniKorn has had a "ready" flag for nodes for a long time, however this flag
> is not set correctly and serves no purpose to the scheduler. In Kubernetes,
> readiness is a far more complex concept anyway, and a single true/false value
> is insufficient. Therefore, we should remove the ready flag to simplify the
> interface. This will also fix a minor issue in the Web UI where ready:false
> is shown for newly added nodes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
