[
https://issues.apache.org/jira/browse/MESOS-6766?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-6766:
---------------------------------------
Summary: HealthChecker launches helper binary during each health check
attempt. (was: HealthChecker launches helper binary each during health check
attempt.)
> HealthChecker launches helper binary during each health check attempt.
> ----------------------------------------------------------------------
>
> Key: MESOS-6766
> URL: https://issues.apache.org/jira/browse/MESOS-6766
> Project: Mesos
> Issue Type: Improvement
> Affects Versions: 1.1.0, 1.2.0
> Reporter: Alexander Rukletsov
> Labels: health-check, mesosphere
>
> Currently the HealthChecker library launches a helper binary ({{curl}} for
> {{HTTP}}, {{mesos-tcp-connect}} for {{TCP}}, {{<user-command>}} for
> {{COMMAND}}) each time it attempts a health check. While it is unavoidable
> for {{COMMAND}} health checks, for {{HTTP}} and {{TCP}} we can do better. We
> probably can't send requests and try TCP handshakes directly from the
> library, i.e., executor process, because appropriate namespaces should be
> entered, but we can launch the binary only once and keep it running alongside
> the task process till the task is running.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
