You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@yunikorn.apache.org by "Peter Bacsko (Jira)" <ji...@apache.org> on 2024/11/05 14:36:00 UTC
[jira] [Resolved] (YUNIKORN-2964) Enhance the error message "node not eligible"
[ https://issues.apache.org/jira/browse/YUNIKORN-2964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Bacsko resolved YUNIKORN-2964.
------------------------------------
Resolution: Duplicate
> Enhance the error message "node not eligible"
> ---------------------------------------------
>
> Key: YUNIKORN-2964
> URL: https://issues.apache.org/jira/browse/YUNIKORN-2964
> Project: Apache YuniKorn
> Issue Type: Improvement
> Components: shim - kubernetes
> Reporter: Peter Bacsko
> Assignee: Peter Bacsko
> Priority: Minor
>
> When we run plugins in the prefilter phase, we maintain a list of nodes (called "mergedNodes") and we check if the current node is included or not after we run a plugin.
> If the node is not listed, we don't log which plugin made this decision. To enhance supportability, we should include the plugin name in the returned message:
> {noformat}
> mergedNodes = mergedNodes.Merge(nodes)
> if !mergedNodes.AllNodes() && !mergedNodes.NodeNames.Has(node.Node().Name) {
> return framework.NewStatus(framework.UnschedulableAndUnresolvable, "node not eligible"), plugin, skip
> } {noformat}
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: dev-help@yunikorn.apache.org