[
https://issues.apache.org/jira/browse/MESOS-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14939696#comment-14939696
]
Tomás Senart commented on MESOS-741:
------------------------------------
I couldn't find a ticket for the development of TCP health checking. Is there
one?
A bit of context on my involvement on this: currently Mesos-DNS can serve stale
unhealthy records because of the lack of native Mesos health checks. When we
have these in place, and have at least Marathon delegate their health checks to
Mesos, we'll be in a much better place to have health-aware service discovery.
> 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.3.4#6332)
