[
https://issues.apache.org/jira/browse/MESOS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204931#comment-14204931
]
Jay Buffington commented on MESOS-809:
--------------------------------------
When we fix this we should update the master/http.cpp code which has this:
{noformat}
const string Master::Http::REDIRECT_HELP = HELP(
TLDR(
"Redirects to the leading Master."),
USAGE(
"/master/redirect"),
DESCRIPTION(
"This returns a 307 Temporary Redirect to the leading Master.",
"If no Master is leading (according to this Master), then the",
"Master will redirect to itself.",
"",
"**NOTES:**",
"1. This is the recommended way to bookmark the WebUI when",
"running multiple Masters.",
"2. This is broken currently \"on the cloud\" (e.g. EC2) as",
"this will attempt to redirect to the private IP address."));
{noformat}
Fixing this issue should resolve #2 in the notes.
> External control of the ip that Mesos components publish to zookeeper
> ---------------------------------------------------------------------
>
> Key: MESOS-809
> URL: https://issues.apache.org/jira/browse/MESOS-809
> Project: Mesos
> Issue Type: Improvement
> Components: framework, master, slave
> Affects Versions: 0.14.2
> Reporter: Khalid Goudeaux
> Priority: Minor
>
> With tools like Docker making containers more manageable, it's tempting to
> use containers for all software installation. The CoreOS project is an
> example of this.
> When an application is run inside a container it sees a different ip/hostname
> from the host system running the container. That ip is only valid from inside
> that host, no other machine can see it.
> From inside a container, the Mesos master and slave publish that private ip
> to zookeeper and as a result they can't find each other if they're on
> different machines. The --ip option can't help because the public ip isn't
> available for binding from within a container.
> Essentially, from inside the container, mesos processes don't know the ip
> they're available at (they may not know the port either).
> It would be nice to bootstrap the processes with the correct ip for them to
> publish to zookeeper.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
