[
https://issues.apache.org/jira/browse/AURORA-377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13989837#comment-13989837
]
Bill Farner commented on AURORA-377:
------------------------------------
Presumably you don't want a TaskEvent but a more useful Veto (which would
surface in the UI). Task events are persistent, and tied to state transitions,
while vetoes are volatile, and associated with inability to schedule. If you
agree, mind tweaking the summary?
> No TaskEvent.message set for a task stuck in PENDING due to host constraints
> ----------------------------------------------------------------------------
>
> Key: AURORA-377
> URL: https://issues.apache.org/jira/browse/AURORA-377
> Project: Aurora
> Issue Type: Bug
> Components: Scheduler
> Reporter: Maxim Khutornenko
>
> Tasks stuck in PENDING state due to unsatisfied host constraint don't have
> the reason set in TaskEvent.message. This makes the troubleshooting harder as
> neither UI nor aurora status can give any clues:
> {noformat}
> INFO] role: mesos, env: test, name: monitoring, shard: 147, status: PENDING
> on None
> cpus: 0.5, ram: 512 MB, disk: 3072 MB
> failure count: 0 (max 1)
> events:
> 2014-05-02 09:05:43 PENDING: None
> metadata:
> package: mesos/monitoring v14
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
