mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Bannier (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-7774) Consider more clearly distinguishing "zombie" tasks from other tasks in webui
Date Mon, 10 Jul 2017 11:29:00 GMT

     [ https://issues.apache.org/jira/browse/MESOS-7774?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Benjamin Bannier updated MESOS-7774:
------------------------------------
    Issue Type: Improvement  (was: Bug)

> Consider more clearly distinguishing "zombie" tasks from other tasks in webui
> -----------------------------------------------------------------------------
>
>                 Key: MESOS-7774
>                 URL: https://issues.apache.org/jira/browse/MESOS-7774
>             Project: Mesos
>          Issue Type: Improvement
>          Components: webui
>            Reporter: Benjamin Bannier
>              Labels: mesosphere
>
> The webui's home page displays a list of active tasks; this list is constructed from
the list of non-completed framework tasks. If a framework has not yet acknowledged a terminal
status update, the list of "active tasks" can contain tasks in terminal states which is confusing
to users, e.g.,
> * launch {{sleep 10}} with {{mesos-execute}}
> * after the task is launch suspend the {{mesos-execute}} process
> * after 10s the list of active tasks contains a {{FINISHED}} task
> or
> * launch {{sleep 100000}} with {{mesos-execute}}
> * after the task is launch suspend the {{mesos-execute}} process
> * kill the {{sleep}} system process
> * the list of active tasks contains a {{FAILED}} task
> The underlying issue here is that what is displayed in the webui very directly reflects
the list of tasks in {{master}} {{Framework}} objects. There {{tasks}} holds tasks the master
needs to track (since they might e.g., still be running, or the frameworks need to be notified
of status changes, etc.), while e.g. {{completedTasks}} holds tasks of just historic interest
since they do not anymore require any master actions.
> Exposing this information in such an unfiltered way is likely confusing. While this applies
to the {{state}} endpoint like it does to the webui, a fix should be easier to accomplish
in the ui. We could there add some (visual?) clue that active tasks in terminal states are
analogous to zombie processes.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message