[
https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14727678#comment-14727678
]
Naganarasimha G R commented on YARN-4106:
-----------------------------------------
Thanks for the thoughts [~leftnoteasy],
Initially we also thought of the same approach but only thing is: At design
level NMDistributedNodeLabelsHandler just asks for labels from provider and
AbstractNodeLabelsProvider has the configuration of fetch-interval which
periodically fetches the labels using the timer, so design wise would it be
better to use the fetch-interval configuration in
NMDistributedNodeLabelsHandler for only in the failure case ? or is it good to
introduce some new configuration only for failure case here, thoughts ?
> 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
> Priority: Critical
>
> 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 message was sent by Atlassian JIRA
(v6.3.4#6332)
