[
https://issues.apache.org/jira/browse/AURORA-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017261#comment-14017261
]
David McLaughlin edited comment on AURORA-495 at 6/3/14 11:40 PM:
------------------------------------------------------------------
Discussed offline with [~kevints] and [~maxim111333]. The issue is that the set
of Vetos for a particular task are mutable - potentially updated while the
state is in PENDING - and are cleared from memory when the task leaves PENDING.
This means they don't fit well with the immutable TaskEvent model.
So we agreed on a new API response that the UI should call to get the taskVetos
separately. From there, the client can add the logic that used to be in the
server above.
was (Author: davmclau):
Discussed offline with [~kevints] and [~maxim111333]. The issue is that the set
of Vetos for a particular task are mutable - potentially updated while the
state is in PENDING - and are cleared from memory when the task leaves PENDING.
This means they don't fit well with the immutable TaskEvent model.
So we agreed on a new API response that the UI should call to get the taskVetos
separately.
> 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
> Attachments: Screen Shot 2014-06-03 at 12.52.21 PM.png
>
>
> 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)
