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 CEDE911197 for ; Thu, 21 Aug 2014 01:41:22 +0000 (UTC) Received: (qmail 64945 invoked by uid 500); 21 Aug 2014 01:41:22 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 64898 invoked by uid 500); 21 Aug 2014 01:41:22 -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 64887 invoked by uid 99); 21 Aug 2014 01:41:22 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Aug 2014 01:41:22 +0000 Date: Thu, 21 Aug 2014 01:41:22 +0000 (UTC) From: "Wangda Tan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (YARN-796) Allow for (admin) labels on nodes and resource-requests 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-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14104926#comment-14104926 ] Wangda Tan commented on YARN-796: --------------------------------- bq. As I've said before, I basically want something similar to the health check code: I provide something executable that the NM can run at runtime that will provide the list of labels. If we need to add labels, it's updating the script which is a much smaller footprint than redeploying HADOOP_CONF_DIR everywhere. I understand now, it's meaningful since it's a flexible way for admin to set labels in NM side. Maybe add a {{NodeLabelCheckerService}} to NM similar to {{NodeHealthCheckerService}} should work. I'll create a separated JIRA for setting labels in NM side under this ticket and leave design/implementation discussion here. > Allow for (admin) labels on nodes and resource-requests > ------------------------------------------------------- > > Key: YARN-796 > URL: https://issues.apache.org/jira/browse/YARN-796 > Project: Hadoop YARN > Issue Type: Sub-task > Affects Versions: 2.4.1 > Reporter: Arun C Murthy > Assignee: Wangda Tan > Attachments: LabelBasedScheduling.pdf, Node-labels-Requirements-Design-doc-V1.pdf, Node-labels-Requirements-Design-doc-V2.pdf, YARN-796.node-label.demo.patch.1, YARN-796.patch, YARN-796.patch4 > > > It will be useful for admins to specify labels for nodes. Examples of labels are OS, processor architecture etc. > We should expose these labels and allow applications to specify labels on resource-requests. > Obviously we need to support admin operations on adding/removing node labels. -- This message was sent by Atlassian JIRA (v6.2#6252)