You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Pankaj Saha <ps...@binghamton.edu> on 2016/05/23 18:18:18 UTC
Mesos installation in cloud network fails when zookeeper elects a
master with internal ip
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
Re: Mesos installation in cloud network fails when zookeeper elects a
master with internal ip
Posted by haosdent <ha...@gmail.com>.
>Here I am facing another issue in mesos master installation. I am passing
> internal ip address to /etc/mesos-master/hostname and ip files in each
> master node.
>
> my hostname and ip file looks like:
> 10.40.0.128
Hi, @Pankaj You could not use same hostname and ip in each master node.
Instead,
you should use the corresponding ip and hostname of your master machine.
And make
sure those ip could be accessed in your env.
On Wed, May 25, 2016 at 1:22 AM, Pankaj Saha <ps...@binghamton.edu> wrote:
> got it thanks.
>
> Here I am facing another issue in mesos master installation. I am passing
> internal ip address to /etc/mesos-master/hostname and ip files in each
> master node.
> I can not start mesos-master with web UI at any of the nodes in
> the presence of hostname and ip file in /etc/mesos-master directory.
>
> my hostname and ip file looks like:
>
> > 10.40.0.128
>
>
> my /etc/zookeeper/zoo.cfg configuration looks like:
>
>
> > server.1=10.40.0.128:2888:3888
> > server.2=10.40.0.129:2888:3888
> > server.3=10.40.0.130:2888:3888
>
>
> my /etc/mesos/zk file looks like :
>
> > zk://10.40.0.128:2181,10.40.0.129:2181,10.40.0.130:2181/mesos
>
>
> But if I remove hostname and ip file from /etc/mesos-master directory, I am
> able to open web UI for each mesos-master but none of them are connected.
> Each portals say "No master is currently leading ..."
>
> Please help.
>
> Thanks
> Pankaj
>
>
> On Mon, May 23, 2016 at 4:28 PM, Arslan Abbasi <ar...@gmail.com>
> wrote:
>
> > The /etc/hosts file should be edited on the machine where you are
> accessing
> > the GUI for Mesos. All the Master Nodes should have no idea about the
> > floating IPs
> >
> >
> >
> > On Mon, May 23, 2016 at 1:21 PM, Pankaj Saha <ps...@binghamton.edu>
> > wrote:
> >
> > > Thanks Arslan,
> > > Okay, so you mean to change the /etc/host file changes to all master
> > nodes
> > > and provide the assigned floating ip to them. I will try and will let
> you
> > > know.
> > >
> > > my understanding was, zookeeper picks the ip address of the
> mesos-master
> > > host from /etc/mesos-master/hostname file.
> > >
> > > On Mon, May 23, 2016 at 4:07 PM, Arslan Abbasi <
> > arslan.abbasi13@gmail.com>
> > > wrote:
> > >
> > > > 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 <psaha4@binghamton.edu
> >
> > > > 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
> > > > >
> > > >
> > >
> >
>
--
Best Regards,
Haosdent Huang
Re: Mesos installation in cloud network fails when zookeeper elects a
master with internal ip
Posted by Pankaj Saha <ps...@binghamton.edu>.
got it thanks.
Here I am facing another issue in mesos master installation. I am passing
internal ip address to /etc/mesos-master/hostname and ip files in each
master node.
I can not start mesos-master with web UI at any of the nodes in
the presence of hostname and ip file in /etc/mesos-master directory.
my hostname and ip file looks like:
> 10.40.0.128
my /etc/zookeeper/zoo.cfg configuration looks like:
> server.1=10.40.0.128:2888:3888
> server.2=10.40.0.129:2888:3888
> server.3=10.40.0.130:2888:3888
my /etc/mesos/zk file looks like :
> zk://10.40.0.128:2181,10.40.0.129:2181,10.40.0.130:2181/mesos
But if I remove hostname and ip file from /etc/mesos-master directory, I am
able to open web UI for each mesos-master but none of them are connected.
Each portals say "No master is currently leading ..."
Please help.
Thanks
Pankaj
On Mon, May 23, 2016 at 4:28 PM, Arslan Abbasi <ar...@gmail.com>
wrote:
> The /etc/hosts file should be edited on the machine where you are accessing
> the GUI for Mesos. All the Master Nodes should have no idea about the
> floating IPs
>
>
>
> On Mon, May 23, 2016 at 1:21 PM, Pankaj Saha <ps...@binghamton.edu>
> wrote:
>
> > Thanks Arslan,
> > Okay, so you mean to change the /etc/host file changes to all master
> nodes
> > and provide the assigned floating ip to them. I will try and will let you
> > know.
> >
> > my understanding was, zookeeper picks the ip address of the mesos-master
> > host from /etc/mesos-master/hostname file.
> >
> > On Mon, May 23, 2016 at 4:07 PM, Arslan Abbasi <
> arslan.abbasi13@gmail.com>
> > wrote:
> >
> > > 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 <ps...@binghamton.edu>
> > > 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
> > > >
> > >
> >
>
Re: Mesos installation in cloud network fails when zookeeper elects a
master with internal ip
Posted by Arslan Abbasi <ar...@gmail.com>.
The /etc/hosts file should be edited on the machine where you are accessing
the GUI for Mesos. All the Master Nodes should have no idea about the
floating IPs
On Mon, May 23, 2016 at 1:21 PM, Pankaj Saha <ps...@binghamton.edu> wrote:
> Thanks Arslan,
> Okay, so you mean to change the /etc/host file changes to all master nodes
> and provide the assigned floating ip to them. I will try and will let you
> know.
>
> my understanding was, zookeeper picks the ip address of the mesos-master
> host from /etc/mesos-master/hostname file.
>
> On Mon, May 23, 2016 at 4:07 PM, Arslan Abbasi <ar...@gmail.com>
> wrote:
>
> > 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 <ps...@binghamton.edu>
> > 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
> > >
> >
>
Re: Mesos installation in cloud network fails when zookeeper elects a
master with internal ip
Posted by Pankaj Saha <ps...@binghamton.edu>.
Thanks Arslan,
Okay, so you mean to change the /etc/host file changes to all master nodes
and provide the assigned floating ip to them. I will try and will let you
know.
my understanding was, zookeeper picks the ip address of the mesos-master
host from /etc/mesos-master/hostname file.
On Mon, May 23, 2016 at 4:07 PM, Arslan Abbasi <ar...@gmail.com>
wrote:
> 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 <ps...@binghamton.edu>
> 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
> >
>
Re: Mesos installation in cloud network fails when zookeeper elects a
master with internal ip
Posted by Arslan Abbasi <ar...@gmail.com>.
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 <ps...@binghamton.edu> 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
>