[
https://issues.apache.org/jira/browse/YARN-3132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jian He updated YARN-3132:
--------------------------
Description:
Using an example to explain:
1) Admin specify host1 has label=x
2) node=host1:123 registered
3) Get node-to-label mapping, return host1/host1:123
4) node=host1:123 unregistered
5) Get node-to-label mapping, still returns host1:123
Probably we should remove host1:123 when it becomes deactivated and no directly
label assigned to it (directly assign means admin specify host1:123 has x
instead of host1 has x).
was:
Using an example to explain:
1) Admin specify host1 has label=x
2) node=host1:123 registered
3) Get node-to-label mapping, return host1/host1:123
4) node=host1:123 unregistered
5) Get node-to-label mapping, still returns host1:123
Probably we should remove host1:123 when it becomes deactivated and no directly
label assigned to it (directly assign means admin specify host1:123 has x
instead of host1 has 123).
> RMNodeLabelsManager should remove node from node-to-label mapping when node
> becomes deactivated
> -----------------------------------------------------------------------------------------------
>
> Key: YARN-3132
> URL: https://issues.apache.org/jira/browse/YARN-3132
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: api, client, resourcemanager
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-3132.1.patch
>
>
> Using an example to explain:
> 1) Admin specify host1 has label=x
> 2) node=host1:123 registered
> 3) Get node-to-label mapping, return host1/host1:123
> 4) node=host1:123 unregistered
> 5) Get node-to-label mapping, still returns host1:123
> Probably we should remove host1:123 when it becomes deactivated and no
> directly label assigned to it (directly assign means admin specify host1:123
> has x instead of host1 has x).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
