mesos-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niklas Quarfot Nielsen (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (MESOS-741) Add health checking for tasks
Date Fri, 02 May 2014 01:38:15 GMT

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

Niklas Quarfot Nielsen reassigned MESOS-741:
--------------------------------------------

    Assignee: Niklas Quarfot Nielsen

> Add health checking for tasks
> -----------------------------
>
>                 Key: MESOS-741
>                 URL: https://issues.apache.org/jira/browse/MESOS-741
>             Project: Mesos
>          Issue Type: Story
>          Components: master, slave
>            Reporter: Niklas Quarfot Nielsen
>            Assignee: Niklas Quarfot Nielsen
>
> Determining the health of a task during its lifetime (during start up, while it is running,
shutting down etc.) can be considered a more elaborate matter than only observing its process
state.
> The task health might be determined by any combination of observable behavior; for example
the process being listening to a certain range of ports, writing certain files or pipes, responding
to messages, utilizing resources to or below certain thresholds etc.
> It could be a powerful extension to extend the interface for launching and running tasks
by an optional HealthCommand message. This message could encode:
> 1) A command to be run at the slave to determine the health of the task. The return value
of the command will tell if the task is healthy or unhealthy. 
> 2) An interval which to run the health command.
> In connection with this, it could make sense to introduce new healthy and unhealthy task
states.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message