[
https://issues.apache.org/jira/browse/AURORA-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Maxim Khutornenko updated AURORA-1193:
--------------------------------------
Description:
Mesos may append an optional message with task status update that is currently
surfacing in the UI via TaskEvent. These messages may not be user friendly and
add confusion. One example is "Unregistered executor" issued when Mesos kills
an assigned task that did not have a chance to run yet. While this message does
not constitute a failure it may create an illusion of abnormal behavior in an
otherwise normal operation.
Consider filtering/formatting messages in the UI/scheduler to avoid adverse
user experience. The ideal solution should also leverage TaskStatus.reason
field to show additional status details.
was:
Mesos may append an optional message with task status update that is currently
surfacing in the UI via TaskEvent. These messages may not be user friendly and
add confusion. One example is "Unregistered executor" issued when Mesos kills
an assigned task that did not have a chance to run yet. While this message does
not constitute a failure it may create an illusion of abnormal behavior in an
otherwise normal operation.
Consider filtering/formatting messages in the UI/scheduler to avoid adverse
user experience.
> Improve UI task status reporting experience
> -------------------------------------------
>
> Key: AURORA-1193
> URL: https://issues.apache.org/jira/browse/AURORA-1193
> Project: Aurora
> Issue Type: Story
> Reporter: Maxim Khutornenko
> Priority: Minor
>
> Mesos may append an optional message with task status update that is
> currently surfacing in the UI via TaskEvent. These messages may not be user
> friendly and add confusion. One example is "Unregistered executor" issued
> when Mesos kills an assigned task that did not have a chance to run yet.
> While this message does not constitute a failure it may create an illusion of
> abnormal behavior in an otherwise normal operation.
> Consider filtering/formatting messages in the UI/scheduler to avoid adverse
> user experience. The ideal solution should also leverage TaskStatus.reason
> field to show additional status details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
