[
https://issues.apache.org/jira/browse/MESOS-672?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13859823#comment-13859823
]
Jason Dusek commented on MESOS-672:
-----------------------------------
Perhaps it would be ultimately better if each master functioned as a proxying
-- proxying to the leader if it's not the leader, and proxying to each slave
for slave information requests. This would reduce, rather than increase, the
amount of network info needing to be stored and managed by Mesos. If the master
can talk to a slave, it can proxy to it; but it can not necessarily redirect to
it.
> Web UI redirection does not work for hosts whose ip addresses are not
> publicly accessible
> -----------------------------------------------------------------------------------------
>
> Key: MESOS-672
> URL: https://issues.apache.org/jira/browse/MESOS-672
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 0.14.0
> Reporter: Jie Yu
> Assignee: Yan Xu
> Labels: twitter
> Fix For: 0.17.0
>
>
> Web UI redirection does not work for hosts where the local interface address
> is not publicly accessible. For example, with EC2 the redirection will not
> work.
> There are some possible solutions:
> (1) Add a new REST endpoint on the master called 'info'. When master A finds
> out that master B is the leader it hits master B's '/master/info' endpoint to
> get back information about that master including it's (public) hostname.
> - This also requires making sure that each master uses it's public
> hostname which may possibly require adding a --hostname flag (similar to what
> we did on the slave).
> - Alternatively, we could update os::hostname to special case EC2, thus
> making Mesos work "out of the box" without requiring operators to explicitly
> set it to the private hostname.
> (2) Add a 'hostname' field to PID and make sure that stringification of the
> PID uses the hostname. Then master redirection is done by getting the
> hostname of the PID instead of the IP. Note this still requires detecting the
> public hostname using mechanisms mentioned in (1).
> (3) Store a separate ZNode for the public hostname. Patch from Brenden
> Matthews: https://reviews.apache.org/r/11975/
> (4) Store a protobuf blob of 'MasterInfo' in ZooKeeper which includes the
> hostname field (suggested by Vinod Kone in the above review). We have to deal
> with issues with backwards compatibility. When old slaves read the new
> master's data, it deserializes the protobuf blob as a PID; when new slaves
> read the old master's data, it deserializes the PID as protobuf.
> This ticket intends to evaluate these potential solutions and solicit new
> ideas.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
