[
https://issues.apache.org/jira/browse/MESOS-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032793#comment-14032793
]
Timothy Chen commented on MESOS-741:
------------------------------------
We decided to do this since the health checker process is meant to stay alive
with the live of the task as it does health check at a recurring interval time,
which means it will output multiple JSON outputs.
I see that Mesos-usage is simply just writing out one JSON in the end and
exits.
The health check process to do the same will have to separate the JSONs with
newline char, and have more handling on the executor.
Overall I felt using libprocess messaging reduces the need to more code to
handle multiple outputs, and reuses existing messaging layer for this. I think
once we see a need for composing it with another interface/tool we can then
modify it. Let me know what you think.
> 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: Timothy Chen
>
> 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)
