[
https://issues.apache.org/jira/browse/MESOS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13768439#comment-13768439
]
Marton Balassi commented on MESOS-435:
--------------------------------------
Have you tried launching the cluster by calling mesos-master and mesos-slave
from sbin and passing the --ip argument for both as suggested here?
https://groups.google.com/forum/#!topic/spark-users/BN94h0AjPdY
Recently tackled the same problem with this solution.
> 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
> Assignee: Benjamin Hindman
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
