Hi I am using solrCloud which uses an ensemble of 3 zookeeper instances.
I am performing survivability tests:
Taking one of the zookeeper instances down I would expect the client to use a
different zookeeper server instance.
But as you can see in the below logs attached
Depending on which
What was the list of servers that was given originally to open the
connection to ZK?
On Tue, Sep 14, 2010 at 6:15 AM, Yatir Ben Shlomo yat...@outbrain.comwrote:
Hi I am using solrCloud which uses an ensemble of 3 zookeeper instances.
I am performing survivability tests:
Taking one of the
zook1:2181,zook2:2181,zook3:2181
-Original Message-
From: Ted Dunning [mailto:ted.dunn...@gmail.com]
Sent: Tuesday, September 14, 2010 4:11 PM
To: zookeeper-user@hadoop.apache.org
Subject: Re: possible bug in zookeeper ?
What was the list of servers that was given originally to open
Hi yatir,
Can you confirm that zook1 , zook2 can be nslookedup from the client
machine?
We havent seen a bug like this. It would be great to nail this down.
Thanks
mahadev
On 9/14/10 8:44 AM, Yatir Ben Shlomo yat...@outbrain.com wrote:
zook1:2181,zook2:2181,zook3:2181
-Original
And that you can connect from every client to every server?
On Tue, Sep 14, 2010 at 9:07 AM, Mahadev Konar maha...@yahoo-inc.comwrote:
Hi yatir,
Can you confirm that zook1 , zook2 can be nslookedup from the client
machine?
We havent seen a bug like this. It would be great to nail this
That is unusual. I don't recall anyone reporting a similar issue, and
looking at the code I don't see any issues off hand. Can you try the
following?
1) on that particular zk client machine resolve the hosts zook1/zook2/zook3,
what ip addresses does this resolve to? (try dig)
2) try running the
