mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Rukletsov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-6517) Health checking only on 127.0.0.1 is limiting.
Date Fri, 27 Jan 2017 12:02:24 GMT

    [ https://issues.apache.org/jira/browse/MESOS-6517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15842621#comment-15842621
] 

Alexander Rukletsov commented on MESOS-6517:
--------------------------------------------

My suggestion would be to leave things as is for now and keep this ticket open. When and if
there will be specific use cases reported where health checking on localhost is not enough
(which we should capture in this ticket), we can think about a solution. Until then I'm reluctant
to introduce changes now.

> 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
>              Labels: health-check, mesosphere
>
> 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)

Mime
View raw message