[
https://issues.apache.org/jira/browse/AURORA-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14339671#comment-14339671
]
Maxim Khutornenko commented on AURORA-1148:
-------------------------------------------
This change improves reporting accuracy by avoiding mixing "heavier" and
"lighter" vetoes within the same offer/task match attempt:
https://reviews.apache.org/r/31525/.
> 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)
