[
https://issues.apache.org/jira/browse/YARN-4176?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14802943#comment-14802943
]
Naganarasimha G R commented on YARN-4176:
-----------------------------------------
[[email protected]],
Thanks for the comments, but based on the earlier comment
bq. Clock-wise, how about adding a new method, `monotonicTimeMillis()`, which
is just nanoTime/1e6; easy to switch from one to the other.
i thought by {{nanoTime/1e6}} you meant {{System.nanoTime()/1000000}}, which is
similar to the modification which you had asked to
[refer|https://github.com/apache/incubator-slider/blob/develop/slider-core/src/main/java/org/apache/slider/common/tools/Duration.java]
but if that also is inconsistent, then any other option ?
[~bibinchundatt],
Missed one more point let the interval configuration name be
{{yarn.nodemanager.node-labels.resync-interval-ms}} , as configurations after
provider was used only for config and label based provider.
> 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)
