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

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

+1, Applied the latest patch, ran the test cases and applied YARN-2729 on top 
of this patch and script was also running successfully. Latest patch LGTM. 
[~leftnoteasy] As far as this patch its fine but was wondering to increase 
usability do we need to support YARN-2728, ??Support for disabling the 
Centralized NodeLabel validation in Distributed Node Label Configuration 
setup?? ?

> 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
>         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