BTW one other observation; when I use 3 clients in the same JVM (i.e.
3 separate instances of ZooKeeper to try simulate a set of different
processes) I find that each client receives an initial WatchEvent on
startup; then from that point on, only the first 2 clients receive
further watch events for
2008/7/22 Flavio Junqueira <[EMAIL PROTECTED]>:
> James, I'd like to clarify what exactly is the issue you're looking at. If
> you provide a list of ZooKeeper servers, then a client will try to reconnect
> to another ZooKeeper server upon a disconnection. Reconnecting to another
> server does not g
ou can do it by just changing the client, since the
> servers might have expired the old session.
>
> Cheers,
> -Flavio
>
>
>> -Original Message-
>> From: James Strachan [mailto:[EMAIL PROTECTED]
>> Sent: Tuesday, July 22, 2008 9:09 PM
>> To:
ilto:[EMAIL PROTECTED]
> Sent: Tuesday, July 22, 2008 9:09 PM
> To: zookeeper-dev@hadoop.apache.org
> Subject: things lock up when the client reconnects?
>
> I wonder if anyone else has seen this recently; I've been trying to
> make the WriteLock implementation survive server restar
I wonder if anyone else has seen this recently; I've been trying to
make the WriteLock implementation survive server restarts (i.e.
reconnecting to another ZK server) with some success. See the latest
patch here...
https://issues.apache.org/jira/browse/ZOOKEEPER-78
but I've found I can reliably ge
