You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Bibin A Chundatt (JIRA)" <ji...@apache.org> on 2015/09/19 15:46:04 UTC
[jira] [Updated] (YARN-4176) Resync NM nodelabels with RM every x
interval for distributed nodelabels
[ https://issues.apache.org/jira/browse/YARN-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bibin A Chundatt updated YARN-4176:
-----------------------------------
Attachment: 0001-YARN-4176.patch
Attaching patch for review.
[~Naganarasimha]
# Have taken care of configuration naming .
# Haven't changed Syste.mills as of now.
> Resync NM nodelabels with RM every x interval for distributed nodelabels
> ------------------------------------------------------------------------
>
> Key: YARN-4176
> URL: https://issues.apache.org/jira/browse/YARN-4176
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Bibin A Chundatt
> Assignee: Bibin A Chundatt
> Attachments: 0001-YARN-4176.patch
>
>
> This JIRA is for handling the below set of issue
> # Distributed nodelabels after NM registered with RM if cluster nodelabels are removed and added then NM doesnt resend labels in heartbeat again untils any change in labels
> # NM registration failed with Nodelabels should resend labels again to RM
> The above cases can be handled by resync nodeLabels with RM every x interval
> # Add property {{yarn.nodemanager.node-labels.provider.resync-interval-ms}} and will resend nodelabels to RM based on config no matter what the registration fails or success.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)