Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 10 Apr 2014 13:10:56 +0000 (UTC)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12625983.1357285092338.92661.1397135456280@arcas>
In-Reply-To: <JIRA.12625983.1357285092338@arcas>
References: <JIRA.12625983.1357285092338@arcas>
Subject: [jira] [Updated] (YARN-314) Schedulers should allow resource
 requests of different sizes at the same priority and location
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arun C Murthy updated YARN-314:
-------------------------------

    Fix Version/s:     (was: 2.4.0)
                   2.5.0

> Schedulers should allow resource requests of different sizes at the same priority and location
> ----------------------------------------------------------------------------------------------
>
>                 Key: YARN-314
>                 URL: https://issues.apache.org/jira/browse/YARN-314
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: scheduler
>    Affects Versions: 2.0.2-alpha
>            Reporter: Sandy Ryza
>            Assignee: Sandy Ryza
>             Fix For: 2.5.0
>
>
> Currently, resource requests for the same container and locality are expected to all be the same size.
> While it it doesn't look like it's needed for apps currently, and can be circumvented by specifying different priorities if absolutely necessary, it seems to me that the ability to request containers with different resource requirements at the same priority level should be there for the future and for completeness sake.


--
This message was sent by Atlassian JIRA
(v6.2#6252)