I believe when a new master is elected, the new url contains the Host Name of the newly Elected leader. From the Mesos setup point of view, all the configuration will be done using the *internal IP addresses* but when you try to access the Mesos GUI from the outside, you will access it over the Floating IP/s.
To resolve the IP address of newly elected leader, you can edit your /etc/hosts file, on the machine where you are accessing the Mesos GUI, to contain the hostname to IP mapping for the Mesos Nodes. Note that this would be the floating IP address of the newly elected leader. Hope this helps On Mon, May 23, 2016 at 11:18 AM, Pankaj Saha <[email protected]> wrote: > hello devs, > > I have a situation where I am given 6 nodes to configure mesos cluster(3 > masters 3 slaves) in a chameleon cloud setup. Each of the node has a > floating public ip and an internal ip. > > My setup consists of libraries from mesosphere package. In zookeeper > configuration I have mentioned three internal ip addresses of mesos-master > as zookeepee server in "zoo.cfg" file, and in mesos-master configuration I > have mentioned masters internal ip in etc/mesos-master/ "hostname" and "ip" > file. > > Now after starting all services I can see mesos portal in one of the > mesos-masters-public-ip:5050, But it fails immediately when zookeeper > changes its next leader and fetches internal ip address of the next > mesos-master leader. > > in zookeeper and mesos master configuration I can not put floating public > ip address as those are not known to zookeeper server and mesos nodes. > > Please guide me how can I make the setup working. do I need to make changes > to network configuration or anything else so that zookeeper can elect a > master with public ip. > > > Thanks > Pankaj >
