Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id CD18C184EC for ; Thu, 10 Sep 2015 16:50:02 +0000 (UTC) Received: (qmail 3934 invoked by uid 500); 10 Sep 2015 16:49:46 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 3892 invoked by uid 500); 10 Sep 2015 16:49:46 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 3881 invoked by uid 99); 10 Sep 2015 16:49:46 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 10 Sep 2015 16:49:46 +0000 Date: Thu, 10 Sep 2015 16:49:46 +0000 (UTC) From: "Naganarasimha G R (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-4106) NodeLabels for NM in distributed mode is not updated even after clusterNodelabel addition in RM MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/YARN-4106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14739097#comment-14739097 ] Naganarasimha G R commented on YARN-4106: ----------------------------------------- bq. Without a centralized node partition collection, capacity planning will be not straightforward. yes idea is to still have this collection but only difference being if the labels sent from NM is not present @ RM, then may be Labels Manager can support additional method which adds the missing labels first and then updates the mapping. thoughts? Yes it makes more sense when we support node constraint, but if we want to support more flexibility then we can think of supporting this too. > 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 > Fix For: 2.8.0 > > Attachments: 0001-YARN-4106.patch, 0002-YARN-4106.patch, 0003-YARN-4106.patch, 0004-YARN-4106.patch, 0005-YARN-4106.patch, 0006-YARN-4106.patch, 0007-YARN-4106.patch, 0008-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)