zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Bianchi <jazzist...@gmail.com>
Subject Re: Zookeeper mesos-master on different network
Date Thu, 14 Apr 2016 14:27:50 GMT
However now i perceive a problem with masters.
If i turn off one master on Network A the the master on network B is
elected but after a minute it will disconnect, coming back to the original
one.

2016-04-14 16:26 GMT+02:00 Stefano Bianchi <jazzista88@gmail.com>:

> on openstack security group the ssh port is open.
>
>
> 2016-04-14 16:24 GMT+02:00 Flavio Junqueira <fpj@apache.org>:
>
>> Is it an indication that the SSH port is open and the others aren't?
>>
>> -Flavio
>>
>> > On 14 Apr 2016, at 15:10, Stefano Bianchi <jazzista88@gmail.com> wrote:
>> >
>> > I tried with telnet and i have connection timed out, but i am able to
>> > connect trough SSH
>> >
>> > 2016-04-14 16:05 GMT+02:00 Stefano Bianchi <jazzista88@gmail.com>:
>> >
>> >> Thanks for your reply Flavio.
>> >> Actually, i don't have a DNS, so i am foced to type hosts file, in
>> which i
>> >> have set all the IP addrsses.
>> >> Of course for the note in Network B i have set the Floating IP of the
>> >> other 2 slaves in network A associated to their hostname. Actually i
>> don't
>> >> know if it is correct, but at least if i make a ping from the slave in
>> >> Network B to a slave in A i obtain replies. and vice versa.
>> >>
>> >> 2016-04-14 15:55 GMT+02:00 Flavio Junqueira <fpj@apache.org>:
>> >>
>> >>> Have you made sure that a slave in net B is able to telnet or ssh to
>> the
>> >>> leader machine in net A? Is it possible that the client port is
>> blocker
>> >>> from B to A?
>> >>>
>> >>> -Flavio
>> >>>
>> >>>
>> >>>> On 14 Apr 2016, at 14:09, Stefano Bianchi <jazzista88@gmail.com>
>> wrote:
>> >>>>
>> >>>> Hi all
>> >>>> i'm working on OpenStack and i have build come virtual machines
and 2
>> >>>> different networks with it.
>> >>>> I have set two mesos clusters:
>> >>>>
>> >>>> NetworkA:
>> >>>> 2 mesos master
>> >>>> 2 mesos slaves
>> >>>>
>> >>>> NetworkB:
>> >>>> 1 mesos master
>> >>>> 1 mesos slave
>> >>>>
>> >>>> I should try to make and interconnection between these two clusters.
>> >>>>
>> >>>> I have set zookeeper configurations such that all 3 masters are
>> >>> competing
>> >>>> for he leadership. I show you the main configurations:
>> >>>>
>> >>>> NetworkA on both 2 masters:
>> >>>>
>> >>>> */etc/zookeeper/conf/zoo.cfg *: at the end of the file
>> >>>>
>> >>>> server.1=192.168.100.54:2888:3888 (master1 on network A)
>> >>>>
>> >>>> server.2=192.168.100.55:2888:3888 (master2 on network A)
>> >>>>
>> >>>> server.3=131.154.xxx.xxx:2888:3888 (Master3 on network B, i have
set
>> >>>> floating IP)
>> >>>>
>> >>>> *etc/mesos/zk*
>> >>>>
>> >>>> zk://192.168.100.54:2181,192.168.100.55:2181
>> ,131.154.xxx.xxx:2181/mesos
>> >>>>
>> >>>> NetorkB:
>> >>>>
>> >>>> */etc/zookeeper/conf/zoo.cfg: at the end of the file:*
>> >>>>
>> >>>> server.1=131.154.96.27:2888:3888 (master1 on network A, i have set
>> >>> floating
>> >>>> IP)
>> >>>>
>> >>>> server.2=131.154.96.32:2888:3888 (master2 on network A, i have set
>> >>> floating
>> >>>> IP)
>> >>>>
>> >>>> server.3=192.168.10.11:2888:3888 (Master3 on network B)
>> >>>>
>> >>>>
>> >>>> *etc/mesos/zk:*
>> >>>>
>> >>>> zk://131.154.zzz.zzz:2181,131.154.yyy.yyy:2181,
>> 192.168.10.11:2181/mesos
>> >>>>
>> >>>>
>> >>>> the 3 masters seems to work fine, if i stop mesos-master service
on
>> one
>> >>> of
>> >>>> them, there is the rielection, so they are behaving as one single
>> >>> cluster
>> >>>> with 3 masters.
>> >>>> I have no problems with masters, but with slaves.
>> >>>> I have currenty set up slaves setting the /etc/mesos/zk exactly
as i
>> >>> shown
>> >>>> above in a coherent way.
>> >>>>
>> >>>> Now the leader s one master which is on the Network A, and only
the
>> >>> slaves
>> >>>> on Network A can connect to it, but i need to connect also the slave
>> on
>> >>> the
>> >>>> other network.
>> >>>> Do you have suggestions?
>> >>>
>> >>>
>> >>
>>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message