You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by "Shingo Omura (JIRA)" <ji...@apache.org> on 2013/07/31 07:13:48 UTC
[jira] [Commented] (MESOS-435) Issue using public IPs or hostnames
for master / slave communication.
[ https://issues.apache.org/jira/browse/MESOS-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724875#comment-13724875 ]
Shingo Omura commented on MESOS-435:
------------------------------------
I succeeded to create an environment which master keeps add and remove slaves.
You can reproduce this environment on your laptop only with vagrant and virtual box.
The environment will be constructed using with virtual private network in virtual box.
Each virtual machine has two NIC interfaces.
One is a bridge to host OS. The other is virtual NIC for virtual private network.
I comment this because I think this would be helpful to investigate the reason of this bug.
Please refer to multi nodes environment of my vagrant-mesos repo.
https://github.com/everpeace/vagrant-mesos
> 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