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

Health checking only on 127.0.0.1 is limiting.

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Open
    • Major
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      As of Mesos 1.1.0, HTTP and TCP health checks always use 127.0.0.1 as the target IP. This is not configurable. As a result, tasks should listen on all interfaces if they want to support HTTP and TCP health checks. However, there might be some cases where tasks or containers will end up binding to a specific IP address.

      To make health checking more robust we can:

      • look at all interfaces in a given network namespace and do health check on all the IP addresses;
      • allow users to specify the IP to health check;
      • deduce the target IP from task's discovery information.

      Attachments

        Activity

          People

            Unassigned Unassigned
            alexr Alex R
            Votes:
            3 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated: