Mailing-List: contact issues-help@aurora.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@aurora.incubator.apache.org
Date: Mon, 2 Mar 2015 18:00:14 +0000 (UTC)
From: "Maxim Khutornenko (JIRA)" <jira@apache.org>
To: issues@aurora.incubator.apache.org
Message-ID: <JIRA.12777440.1424852166000.53693.1425319214828@Atlassian.JIRA>
In-Reply-To: <JIRA.12777440.1424852166000@Atlassian.JIRA>
References: <JIRA.12777440.1424852166000@Atlassian.JIRA>
 <JIRA.12777440.1424852166805@arcas>
Subject: [jira] [Updated] (AURORA-1148) Display All Scheduling Veto Reasons
 for PENDING tasks
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Maxim Khutornenko updated AURORA-1148:
--------------------------------------
    Sprint: Twitter Aurora Q1'15 Sprint 4

> Display All Scheduling Veto Reasons for PENDING tasks
> -----------------------------------------------------
>
>                 Key: AURORA-1148
>                 URL: https://issues.apache.org/jira/browse/AURORA-1148
>             Project: Aurora
>          Issue Type: Story
>          Components: Reliability, Scheduler
>            Reporter: Joe Smith
>
> Recently I was triaging an instance that would not schedule, and although I was validating many possibilities, I did get sidetracked when I saw that 'Insufficient RAM' was listed as the reason.
> In fact, there was also insufficient Disk, CPU, and hosts, as this was a task which had a dedicated constraint.
> In order to give more information, we should ensure we're exposing all Vetoes to help narrow if there is just one resource preventing scheduling, or many (all resources may point to a lack of hosts overall, for instance).
> I did notice both AURORA-377 and AURORA-911, but both seem unrelated to this.


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