[
https://issues.apache.org/jira/browse/YARN-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14791827#comment-14791827
]
Bibin A Chundatt commented on YARN-4176:
----------------------------------------
Hi [~Naganarasimha]
Thnks for the comments.
{quote}
I would suggest only to have only 1 resync configuration and remove what we
introduced for YARN-4106.
{quote}
Will be taken care
{quote}
So node labels will be sent to RM either if node labels are modified since the
last heartbeat or the resync-interval has elapsed right ?
{quote}
Currently on hearbeat we are sending only when update happens. Will be *or* of
update & resync.
Changing to {{System.nanoTime()}} will handle too.
> 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
>
> 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)
