[
https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14730380#comment-14730380
]
Naganarasimha G R commented on YARN-4106:
-----------------------------------------
[~bibinchundatt],
Good catch, Basically this was added initially for testing and later removed
but got missed over here so basically its sufficient that {{intervalTime}}
itself is used as {{delay}} in {{AbstractNodeLabelsProvider.serviceStart}} and
also we can remove {{startTime}} & in
{{ConfigurationNodeLabelsProvider.serviceInit}} we can remove {{startTime}} and
instead of calling {{updateNodeLabelsFromConfig}} in {{serviceInit}} we can
override and invoke {{timertask.run}} in {{serviceStart()}}. Please correct the
test cases accordingly.
> 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
> Attachments: 0001-YARN-4106.patch, 0002-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 message was sent by Atlassian JIRA
(v6.3.4#6332)
