[
https://issues.apache.org/jira/browse/MESOS-5727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Rukletsov updated MESOS-5727:
---------------------------------------
Description:
Since we launch the task after pivot_root, we no longer has the access to the
mesos-health-check binary. The solution is to refactor health check to be a
library (libprocess) so that it does not depend on the underlying filesystem.
One note here is that we should strive to keep both the command executor and
the task in the same mount namespace so that Mesos CLI tooling does not need to
find the mount namespace for the task. It just need to find the corresponding
pid for the executor. This statement is *arguable*, see the comment below.
was:
Since we launch the task after pivot_root, we no longer has the access to the
mesos-health-check binary. The solution is to refactor health check to be a
library (libprocess) so that it does not depend on the underlying filesystem.
One note here is that we should strive to keep both the command executor and
the task in the same mount namespace so that Mesos CLI tooling does not need to
find the mount namespace for the task. It just need to find the corresponding
pid for the executor.
> Command executor health check does not work when the task specifies container
> image.
> ------------------------------------------------------------------------------------
>
> Key: MESOS-5727
> URL: https://issues.apache.org/jira/browse/MESOS-5727
> Project: Mesos
> Issue Type: Bug
> Components: containerization
> Affects Versions: 0.28.2, 1.0.0
> Reporter: Jie Yu
> Assignee: Gilbert Song
> Labels: containerizer, health-check, mesosphere
> Fix For: 1.0.0
>
>
> Since we launch the task after pivot_root, we no longer has the access to the
> mesos-health-check binary. The solution is to refactor health check to be a
> library (libprocess) so that it does not depend on the underlying filesystem.
> One note here is that we should strive to keep both the command executor and
> the task in the same mount namespace so that Mesos CLI tooling does not need
> to find the mount namespace for the task. It just need to find the
> corresponding pid for the executor. This statement is *arguable*, see the
> comment below.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
