You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Alexander Rukletsov (JIRA)" <ji...@apache.org> on 2016/10/31 17:19:58 UTC

[jira] [Created] (MESOS-6517) Health checking only on 127.0.0.1 is limiting.

Alexander Rukletsov created MESOS-6517:
------------------------------------------

             Summary: Health checking only on 127.0.0.1 is limiting.
                 Key: MESOS-6517
                 URL: https://issues.apache.org/jira/browse/MESOS-6517
             Project: Mesos
          Issue Type: Improvement
            Reporter: Alexander Rukletsov


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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)