No worries, let us know if something else pops up.
Patrick
On Tue, Sep 7, 2010 at 3:10 PM, Stack st...@duboce.net wrote:
Nevermind. I figured it. It was an hbase issue. We were leaking a
client reference.
Sorry for the noise,
St.Ack
On Sat, Sep 4, 2010 at 10:58 AM, Stack
No worries, let us know if something else pops up.
Patrick
On Tue, Sep 7, 2010 at 3:10 PM, Stack st...@duboce.net wrote:
Nevermind. I figured it. It was an hbase issue. We were leaking a
client reference.
Sorry for the noise,
St.Ack
On Sat, Sep 4, 2010 at 10:58 AM, Stack
Hi All,
Can you please share your experience regarding ZK snapshot retention and
recovery policies?
We have an application where we never need to rollback (i.e., revert back to
a previous state by using old snapshots). Given this, I am trying to
understand under what circumstances would we ever
4) This was brought up on the list recently: is there a strategy for
managing the ensemble member replacment problem? It's pretty
undesirable to restart clients to learn about a replaced machine.
We've implemented a patch on the C client that allows for modifying
the server list at
This would be the ideal solution to this problem I think.
Poking around the (3.3) code to figure out how hard it would be to implement, I
figure one way to do it would be to modify the session timeout to the min
session timeout and touch the connection before calling close when you get
certain
unfortunately, that only works on the standalone server.
ben
On 09/08/2010 12:52 PM, Fournier, Camille F. [Tech] wrote:
This would be the ideal solution to this problem I think.
Poking around the (3.3) code to figure out how hard it would be to implement, I
figure one way to do it would be to
To get it to work in a cluster, what would be necessary?
A new message to the leader to describe connection loss?
On Wed, Sep 8, 2010 at 1:03 PM, Benjamin Reed br...@yahoo-inc.com wrote:
unfortunately, that only works on the standalone server.
ben
On 09/08/2010 12:52 PM, Fournier, Camille
Yes, Ben, would you give some more details as to why it doesn't work in a
cluster? I think I am seeing it work ok in cluster mode as well with some basic
tests. There are probably other major problems with this but I would appreciate
any direction you could give as to what might go wrong here.
Hi all,
I am new to ZK and using the queue and lock examples that come with
zookeeper but have run into ZOOKEEPER-645 with the lock.
I have several JVMs each keeping a long running ZK client and the
first JVM (and hence client) does not respect the locks obtained by
subsequent clients - e.g. the
