You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Niklas Quarfot Nielsen (JIRA)" <ji...@apache.org> on 2014/05/02 03:44:19 UTC

[jira] [Commented] (MESOS-741) Add health checking for tasks

    [ https://issues.apache.org/jira/browse/MESOS-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13987257#comment-13987257 ] 

Niklas Quarfot Nielsen commented on MESOS-741:
----------------------------------------------

Ben and I am jumping on this ticket.

The initial idea is to support HTTP and TCP checks, however the proposed design can capture more strategies such as running shell commands, checking cpu/memory usage and so on.

Here is an idea for breakdown of this task:

1) Introduce HealthCheck protobuf message and add to CommandInfo

2) Implement 'mesos-health-check' helper executable

3) Have command executor use (2)

4) Have containerizer use (2)

> 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)