Uploaded image for project: 'Mesos'
  1. Mesos
  2. MESOS-6766

HealthChecker launches helper binary during each health check attempt.

Attach filesAttach ScreenshotAdd voteVotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • 1.1.0, 1.2.0
    • None
    • None

    Description

      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.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            Unassigned Unassigned
            alexr Alex R

            Dates

              Created:
              Updated:

              Slack

                Issue deployment