You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Lukas Loesche (JIRA)" <ji...@apache.org> on 2014/12/04 01:31:13 UTC
[jira] [Updated] (MESOS-2170) Choose a sane default interface on startup

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

Lukas Loesche updated MESOS-2170:
---------------------------------
    Description: 
Upon startup (if not explicitly specified) mesos chooses one (the first?) of the available IPs that is not a loopback device.

On my Mac this means that it usually chooses the VirtualBox interface that has no outside connectivity. On Linux it often uses to the IP of the docker0 interface which doesn't make a lot of sense either.

A better default behaviour would be that (if not explicitly specified) mesos should choose the IP of the interface that the default gateway of the system is on. And for mesos-slave it would be good if he chose the source IP he's using to actually communicate with the master (otherwise the master rejects messages from the slave because the source IP of the connection is different from the IP the slave communicates to the master - which is what's happening on my system right now). In all my scenarios that I played through this would always have been the correct IP to use and certainly a better choice than a docker0 or vbox interface.


  was:
Upon startup (if not explicitly specified) mesos chooses one (the first?) of the available IPs that is not a loopback device.

On my Mac this means that it usually binds to VirtualBox interfaces that have no outside connectivity. On Linux it often binds to the IP of the docker0 interface which doesn't make a lot of sense either.

A better default behaviour would be that (if not explicitly specified) mesos should bind to the IP of the interface that the default gateway of the system is on. That is if the system has a default gateway. In all my scenarios that I played through this would always have been the correct IP to bind to and certainly a better choice than a docker0 or vbox interface.



> Choose a sane default interface on startup
> ------------------------------------------
>
>                 Key: MESOS-2170
>                 URL: https://issues.apache.org/jira/browse/MESOS-2170
>             Project: Mesos
>          Issue Type: Improvement
>          Components: general
>    Affects Versions: 0.20.1
>            Reporter: Lukas Loesche
>            Priority: Minor
>
> Upon startup (if not explicitly specified) mesos chooses one (the first?) of the available IPs that is not a loopback device.
> On my Mac this means that it usually chooses the VirtualBox interface that has no outside connectivity. On Linux it often uses to the IP of the docker0 interface which doesn't make a lot of sense either.
> A better default behaviour would be that (if not explicitly specified) mesos should choose the IP of the interface that the default gateway of the system is on. And for mesos-slave it would be good if he chose the source IP he's using to actually communicate with the master (otherwise the master rejects messages from the slave because the source IP of the connection is different from the IP the slave communicates to the master - which is what's happening on my system right now). In all my scenarios that I played through this would always have been the correct IP to use and certainly a better choice than a docker0 or vbox interface.



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