Return-Path: <yarn-issues-return-105411-archive-asf-public=cust-asf.ponee.io@hadoop.apache.org>
X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io
Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io
Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183])
	by cust-asf2.ponee.io (Postfix) with ESMTP id 1F2AC200BF4
	for <archive-asf-public-internal@cust-asf2.ponee.io>; Fri,  6 Jan 2017 23:17:02 +0100 (CET)
Received: by cust-asf.ponee.io (Postfix)
	id 1DEAC160B37; Fri,  6 Jan 2017 22:17:02 +0000 (UTC)
Delivered-To: archive-asf-public@cust-asf.ponee.io
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by cust-asf.ponee.io (Postfix) with SMTP id 690D6160B49
	for <archive-asf-public@cust-asf.ponee.io>; Fri,  6 Jan 2017 23:17:01 +0100 (CET)
Received: (qmail 78376 invoked by uid 500); 6 Jan 2017 22:16:59 -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>
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 78036 invoked by uid 99); 6 Jan 2017 22:16:59 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jan 2017 22:16:59 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id 59ECE2C1F56
	for <yarn-issues@hadoop.apache.org>; Fri,  6 Jan 2017 22:16:59 +0000 (UTC)
Date: Fri, 6 Jan 2017 22:16:59 +0000 (UTC)
From: "Julia Sommer (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.13032310.1483636178000.672437.1483741019365@Atlassian.JIRA>
In-Reply-To: <JIRA.13032310.1483636178000@Atlassian.JIRA>
References: <JIRA.13032310.1483636178000@Atlassian.JIRA> <JIRA.13032310.1483636178693@arcas>
Subject: [jira] [Updated] (YARN-6057) yarn.scheduler.minimum-allocation-*
 and yarn.scheduler.maximum-allocation-* descriptions are incorrect about
 behavior when a request is out of bounds
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
archived-at: Fri, 06 Jan 2017 22:17:02 -0000


     [ https://issues.apache.org/jira/browse/YARN-6057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julia Sommer updated YARN-6057:
-------------------------------
    Attachment: YARN-6057.001.patch

Changed description to reflect values getting adjusted to match rather than shooting an error code.

> yarn.scheduler.minimum-allocation-* and yarn.scheduler.maximum-allocation-* descriptions are incorrect about behavior when a request is out of bounds
> -----------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-6057
>                 URL: https://issues.apache.org/jira/browse/YARN-6057
>             Project: Hadoop YARN
>          Issue Type: Bug
>            Reporter: Bibin A Chundatt
>            Assignee: Julia Sommer
>            Priority: Minor
>         Attachments: YARN-6057.001.patch
>
>
> {code}
>   <property>
>     <description>The minimum allocation for every container request at the RM,
>     in terms of virtual CPU cores. Requests lower than this will throw a
>     InvalidResourceRequestException.</description>
>     <name>yarn.scheduler.minimum-allocation-vcores</name>
>     <value>1</value>
>   </property>
> {code}
> *Requests lower than this will throw a   InvalidResourceRequestException.* Only incase of maximum allocation vcore and memory InvalidResourceRequestException is thrown



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

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org