Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Fri, 30 Jan 2015 22:44:35 +0000 (UTC)
From: "Siqi Li (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12770269.1422336126000.219093.1422657875959@Atlassian.JIRA>
In-Reply-To: <JIRA.12770269.1422336126000@Atlassian.JIRA>
References: <JIRA.12770269.1422336126000@Atlassian.JIRA>
 <JIRA.12770269.1422336126374@arcas>
Subject: [jira] [Updated] (YARN-3101) FairScheduler#fitInMaxShare was added
 to validate reservations but it does not consider it
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Siqi Li updated YARN-3101:
--------------------------
    Attachment: YARN-3101-Siqi.v2.patch

> FairScheduler#fitInMaxShare was added to validate reservations but it does not consider it 
> -------------------------------------------------------------------------------------------
>
>                 Key: YARN-3101
>                 URL: https://issues.apache.org/jira/browse/YARN-3101
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>            Reporter: Anubhav Dhoot
>            Assignee: Anubhav Dhoot
>         Attachments: YARN-3101-Siqi.v1.patch, YARN-3101-Siqi.v2.patch, YARN-3101.001.patch, YARN-3101.002.patch
>
>
> YARN-2811 added fitInMaxShare to validate reservations on a queue, but did not count it during its calculations. It also had the condition reversed so the test was still passing because both cancelled each other. 


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