That detail is purposefully not exposed through the client api, however
it is output to the log on connection establishment.
Why would your client code need to know which server in the ensemble it
is connected to?
Patrick
Rob Baccus wrote:
How do I determine the server the client is
Failover testing.
-Original Message-
From: Patrick Hunt [mailto:ph...@apache.org]
Sent: Thursday, October 01, 2009 3:44 PM
To: zookeeper-user@hadoop.apache.org; Rob Baccus
Subject: Re: How do we find the Server the client is connected to?
That detail is purposefully not exposed
Grovel the logs.
On Thu, Oct 1, 2009 at 3:46 PM, Todd Greenwood to...@audiencescience.comwrote:
Failover testing.
-Original Message-
From: Patrick Hunt [mailto:ph...@apache.org]
Sent: Thursday, October 01, 2009 3:44 PM
To: zookeeper-user@hadoop.apache.org; Rob Baccus
Subject:
It's possible, but not pretty.
Try this:
1) create a subclass of ZooKeeper to be used in your tests
2) in the subclass add something like this:
public String getConnectedServer() {
return ((SocketChannel)cnxn.sendThread.sockKey.channel()).socket()
Possible, but very ugly. I do something similar to this in zk tests:
org.apache.zookeeper.server.quorum.QuorumPeerMainTest.testBadPeerAddressInQuorum()
if you want to see an example.
Patrick
Ted Dunning wrote:
Grovel the logs.
On Thu, Oct 1, 2009 at 3:46 PM, Todd Greenwood
