Return-Path: 
 <yarn-issues-return-81439-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 7221718CB3
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Fri, 11 Mar 2016 14:07:00 +0000 (UTC)
Received: (qmail 51606 invoked by uid 500); 11 Mar 2016 14:07:00 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 51557 invoked by uid 500); 11 Mar 2016 14:07:00 -0000
Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-issues@hadoop.apache.org>
List-Id: <yarn-issues.hadoop.apache.org>
Reply-To: yarn-issues@hadoop.apache.org
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 51544 invoked by uid 99); 11 Mar 2016 14:06:59 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Mar 2016 14:06:59 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id D9C3D2C1F54
	for <yarn-issues@hadoop.apache.org>; Fri, 11 Mar 2016 14:06:59 +0000 (UTC)
Date: Fri, 11 Mar 2016 14:06:59 +0000 (UTC)
From: "Junping Du (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12625973.1357272242000.1368.1457705219885@Atlassian.JIRA>
In-Reply-To: <JIRA.12625973.1357272242000@Atlassian.JIRA>
References: <JIRA.12625973.1357272242000@Atlassian.JIRA>
 <JIRA.12625973.1357272242982@arcas>
Subject: [jira] [Updated] (YARN-313) Add Admin API for supporting node
 resource configuration in command line
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-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Junping Du updated YARN-313:
----------------------------
    Release Note: 
After this patch, the feature to support NM resource dynamically configuration is completed, so that user can configure NM with new resource without bring NM down or decommissioned.
Two CLIs are provided to support update resources on individual node or a batch of nodes:
1. Update resource on single node: yarn rmadmin -updateNodeResource [NodeID] [MemSize] [vCores] 
2. Update resource on a batch of nodes: yarn rmadmin -refreshNodesResources, that reflect nodes' resource configuration defined in dynamic-resources.xml which is loaded by RM dynamically (like capacity-scheduler.xml or fair-scheduler.xml). 
The first version of configuration format is:
<configuration>
  <property>
    <name>yarn.resource.dynamic.nodes</name>
    <value>h1:1234</value>
  </property>
  <property>
    <name>yarn.resource.dynamic.h1:1234.vcores</name>
    <value>16</value>
  </property>
  <property>
    <name>yarn.resource.dynamic.h1:1234.memory</name>
    <value>1024</value>
  </property>
</configuration> 

  was:
Since this patch, we are providing CLI to support NM resource dynamically configuration that user can configure NM with new resource without bring NM down or decommissioned.
Two CLIs are provided to support update resources on individual node or a batch of nodes:
1. Update resource on single node: yarn rmadmin -updateNodeResource [NodeID] [MemSize] [vCores] 
2. Update resource on a batch of nodes: yarn rmadmin -refreshNodesResources, that reflect nodes' resource configuration defined in dynamic-resources.xml, the format of configuration is get optimized in YARN-4160.


> Add Admin API for supporting node resource configuration in command line
> ------------------------------------------------------------------------
>
>                 Key: YARN-313
>                 URL: https://issues.apache.org/jira/browse/YARN-313
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: client, graceful
>            Reporter: Junping Du
>            Assignee: Inigo Goiri
>            Priority: Critical
>             Fix For: 2.8.0
>
>         Attachments: YARN-313-sample.patch, YARN-313-v1.patch, YARN-313-v10.patch, YARN-313-v11.patch, YARN-313-v2.patch, YARN-313-v3.patch, YARN-313-v4.patch, YARN-313-v5.patch, YARN-313-v6.patch, YARN-313-v7.patch, YARN-313-v8.patch, YARN-313-v9.patch
>
>
> We should provide some admin interface, e.g. "yarn rmadmin -refreshResources" to support changes of node's resource specified in a config file.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)