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/02 07:56:46 UTC
[jira] [Commented] (YARN-4106) NodeLabels for NM in distributed
mode is not updated even after clusterNodelabel addition in RM
[ https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14726802#comment-14726802 ]
Bibin A Chundatt commented on YARN-4106:
----------------------------------------
Observation
=========
Logs shown below are when Cluster node labels are not available in RM
{code}
2015-09-02 10:21:02,766 ERROR org.apache.hadoop.yarn.server.nodemanager.NodeStatusUpdaterImpl: Node Labels {1} reported from NM with ID host-<HOSTNAME>:64318 was rejected from RM with exception message as : Not all labels being replaced contained by known label collections,
please check, new labels=[1]
{code}
# On restart of NM its updating fine
# Looks like once failure happens NM not resending nodelabel status in heartbeat to RM
> 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
>
> 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)