[
https://issues.apache.org/jira/browse/AURORA-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016100#comment-14016100
]
David McLaughlin commented on AURORA-495:
-----------------------------------------
So the struct for TaskEvent is:
{code}
// Event marking a state transition within a task's lifecycle.
struct TaskEvent {
// Epoch timestamp in milliseconds.
1: i64 timestamp
// New status of the task.
2: ScheduleStatus status
// Audit message that explains why a transition occurred.
3: optional string message
// Hostname of the scheduler machine that performed the event.
4: optional string scheduler
}
{code}
So we could:
1) fill the message field there when the task is stored using the logic above.
2) fill the message field before returning to the user using the logic above.
3) create a new response type that has an extra field just for pending reasons.
(3) only seems necessary if pending task events can have legitimate messages
other than their reason for being pending. So far I haven't seen any examples
of this.
> UI should always show a pending reason
> --------------------------------------
>
> Key: AURORA-495
> URL: https://issues.apache.org/jira/browse/AURORA-495
> Project: Aurora
> Issue Type: Bug
> Components: Scheduler, UI
> Reporter: Suman Karumuri
> Assignee: David McLaughlin
> Priority: Critical
>
> The pending reason in the UI is empty which leaves the user confused. The
> scheduler should be updated to always show a reason for pending the task.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
