You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@aurora.apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2015/04/17 23:57:58 UTC

[jira] [Resolved] (AURORA-1148) Display All Scheduling Veto Reasons for PENDING tasks

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

Bill Farner resolved AURORA-1148.
---------------------------------
    Resolution: Fixed

I believe AURORA-911 is the closest we should come to addressing what's requested in this ticket.  As Maxim notes, an exhaustive veto list would be daunting and likely counterproductive.

> 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
>            Assignee: Maxim Khutornenko
>
> 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)