[ 
https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739097#comment-14739097
 ] 

Naganarasimha G R commented on YARN-4106:
-----------------------------------------

bq.  Without a centralized node partition collection, capacity planning will be 
not straightforward.
yes idea is to still have this collection but only difference being if the 
labels sent from NM is not present @ RM, then may be Labels Manager can support 
additional method which adds the missing labels first and then updates the 
mapping. thoughts?
Yes it makes more sense when we support node constraint, but if we want to 
support more flexibility then we can think of supporting this too.

> NodeLabels for NM in distributed mode is not updated even after 
> clusterNodelabel addition in RM
> -----------------------------------------------------------------------------------------------
>
>                 Key: YARN-4106
>                 URL: https://issues.apache.org/jira/browse/YARN-4106
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Bibin A Chundatt
>            Assignee: Bibin A Chundatt
>             Fix For: 2.8.0
>
>         Attachments: 0001-YARN-4106.patch, 0002-YARN-4106.patch, 
> 0003-YARN-4106.patch, 0004-YARN-4106.patch, 0005-YARN-4106.patch, 
> 0006-YARN-4106.patch, 0007-YARN-4106.patch, 0008-YARN-4106.patch
>
>
> NodeLabels for NM in distributed mode is not updated even after 
> clusterNodelabel addition in RM
> Steps to reproduce
> ===============
> # Configure nodelabel in distributed mode
> yarn.node-labels.configuration-type=distributed
> provider = config
> yarn.nodemanager.node-labels.provider.fetch-interval-ms=120000ms
> # Start RM the NM
> # Once NM is registration is done add nodelabels in RM
> Nodelabels not getting updated in RM side 
> *This jira also handles the below issue too*
> Timer Task not getting triggered in Nodemanager for Label update in 
> nodemanager for distributed scheduling
> Task is supposed to trigger every 
> {{yarn.nodemanager.node-labels.provider.fetch-interval-ms}}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to