You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "András Győri (Jira)" <ji...@apache.org> on 2022/02/22 14:05:00 UTC
[jira] [Commented] (YARN-11017) Unify node label access in queues
[ https://issues.apache.org/jira/browse/YARN-11017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496106#comment-17496106 ]
András Győri commented on YARN-11017:
-------------------------------------
After reevaluating this issue, I think it is too risky to refactor node label related code paths. Closing it for now.
> Unify node label access in queues
> ---------------------------------
>
> Key: YARN-11017
> URL: https://issues.apache.org/jira/browse/YARN-11017
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: capacity scheduler
> Reporter: Andras Gyori
> Assignee: Andras Gyori
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Currently there are a handful of ways in which queues are able to access node labels. A non-exhaustive list of these are:
> # configuredNodeLabels
> # getNodeLabelsForQueue()
> # QueueCapacities#getNodePartitionsSet()
> # ResourceUsage#getNodePartitionsSet()
> # accessibleNodeLabels
> It is worth revisiting, as there already is a bug, which was implicitly caused by this inconsistency (YARN-11016).
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org