[ https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14735207#comment-14735207 ]
Wangda Tan commented on YARN-4106: ---------------------------------- Thanks update [~bibinchundatt], and comments from [~Naganarasimha]. Few minor comments: 1) Make failLabelResendInterval to final before we can configure it. 2) testConfigTimer sleep time is too much, I don't know if Clock can be used in Timer, I think you can set NM_NODE_LABELS_PROVIDER_FETCH_INTERVAL_MS to lower value, like 1000, and sleep 1500 ms. 3) With changes in your patch, testNodeLabelsFromConfig doesn't need sleep any more? > 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 > > > 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)