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

Posted to dev@mesos.apache.org by "Benjamin Mahler (JIRA)" <ji...@apache.org> on 2013/04/15 20:36:16 UTC

[jira] [Created] (MESOS-435) Issue using public IPs or hostnames for master / slave communication.

Benjamin Mahler created MESOS-435:
-------------------------------------

             Summary: 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