Description
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.
Attachments
Issue Links
- is depended upon by
-
MESOS-1281 Support fall-back in replaceTask with health-checks
-
- Open
-
- relates to
-
MESOS-2533 Support HTTP checks in Mesos.
-
- Resolved
-
-
-
- Resolved
-