[
https://issues.apache.org/jira/browse/MESOS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185771#comment-14185771
]
Dominic Hamon commented on MESOS-435:
-------------------------------------
This seems like a network configuration issue that has valid workarounds using
{{--ip}} or {{--hostname}} flags. Is there work to do here on the
Mesos/libprocess side?
> Issue using public IPs or hostnames for master / slave communication.
> ---------------------------------------------------------------------
>
> Key: MESOS-435
> URL: https://issues.apache.org/jira/browse/MESOS-435
> Project: Mesos
> Issue Type: Bug
> Reporter: Benjamin Mahler
> Labels: twitter
>
> The bug here likely lies within libprocess.
> Often we get reports of no connectivity between the master and slave when
> administrators are setting up a private mesos cluster. It seems that
> specifying public IPs or hostnames have issues, whereas specifying the
> private IPs work.
> This is a common hurdle, here is the latest report:
> http://mail-archives.apache.org/mod_mbox/incubator-mesos-dev/201304.mbox/%3CCADqAWGCQvSRbQtmQDb_Oh%2BW9Sm_%2Bp6pgDLburpw1gE46jOoFtg%40mail.gmail.com%3E
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
