You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@mesos.apache.org by "Avinash Sridharan (JIRA)" <ji...@apache.org> on 2017/10/02 23:02:01 UTC

[jira] [Updated] (MESOS-8050) Mesos HTTP/HTTPS health checks for IPv6 docker containers.

     [ https://issues.apache.org/jira/browse/MESOS-8050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Avinash Sridharan updated MESOS-8050:
-------------------------------------
    Target Version/s: 1.5.0

> Mesos HTTP/HTTPS health checks for IPv6 docker containers.
> ----------------------------------------------------------
>
>                 Key: MESOS-8050
>                 URL: https://issues.apache.org/jira/browse/MESOS-8050
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Avinash Sridharan
>            Assignee: Vinod Kone
>
> Currently the MESOS HTTP/HTTPS health checks hardcode the IP address to 127.0.0.1 while performing the pings on the containers. With IPv6 containers, even dual stack kernels the container will have both the IPv4 and IPv6 loopback interfaces (127.0.0.1 and ::1). Further, its upto the application's discretion to either open a INET or an INET6 socket which would imply that to support IPv6 containers the MESOS HTTP/HTTPS health checks need to be configurable to perform health checks on 127.0.0.1 or ::1. 
> A proposal here would be to introduce the concept of a transport on which MESOS HTTP/HTTPS health checks work. That is the framework specifies whether MESOS HTTP healthchecks work over TCP or TCP6. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)