[
https://issues.apache.org/jira/browse/YARN-7653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16301077#comment-16301077
]
Arun Suresh commented on YARN-7653:
-----------------------------------
One other thing:
{code}
rmContext.getRMNodes().get(nodeId).getRackName()
{code}
That can cause an NPE if the node does not exist. But since it will usually be
called only inside the addContainer, which will be called when the RMContainer
is allocated - the chances are less. But maybe perform a null check to be safe
just to be safe.
> Node group support for AllocationTagsManager
> --------------------------------------------
>
> Key: YARN-7653
> URL: https://issues.apache.org/jira/browse/YARN-7653
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Panagiotis Garefalakis
> Assignee: Panagiotis Garefalakis
> Attachments: YARN-7653-YARN-6592.001.patch,
> YARN-7653-YARN-6592.002.patch, YARN-7653-YARN-6592.003.patch
>
>
> AllocationTagsManager currently supports node and cluster-wide tag
> cardinality retrieval.
> If we want to support arbitrary node-groups/scopes for our placement
> constraints TagsManager should be extended to provide such functionality.
> As a first step we need to support RACK scope cardinality retrieval (as
> defined in our API).
> i.e. how many "spark" containers are currently running on "RACK-1"
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
