[MESOS-5727] Command executor health check does not work when the task specifies container image.

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.28.2, 1.0.0
• Fix Version/s: 1.0.0
• Component/s: containerization
• Labels: containerizer health-check mesosphere
• Epic Link: Unified Container
• Sprint: Mesosphere Sprint 38
• Story Points: 5
• Assignee: Gilbert Song
• Reporter: Jie Yu
• Shepherd: Jie Yu
• Created: 27/Jun/16 23:51
• Updated: 28/Aug/16 15:06
• Resolved: 02/Jul/16 00:02

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.

Issue Links

• relates to: MESOS-2533 Support HTTP checks in Mesos.
• relates to: MESOS-3567 Support TCP checks in Mesos.