Please disregard - Re: Exception on close of connection (WAS - Re: c client on win32)

2009-11-20 Thread stack
Please disregard. Sorry for the noise (Patrick, of note, I am seeing this session timeout on a cluster other than Zhenyus). St.Ack On Fri, Nov 20, 2009 at 4:24 PM, stack st...@duboce.net wrote: Sorry, I had a bad subject on the below question. St.Ack On Fri, Nov 20, 2009 at 4:22 PM, stack st

Re: Please disregard - Re: Exception on close of connection (WAS - Re: c client on win32)

2009-11-20 Thread stack
not cleaning up the ZK session gracefully via close()? Patrick stack wrote: Please disregard. Sorry for the noise (Patrick, of note, I am seeing this session timeout on a cluster other than Zhenyus). St.Ack On Fri, Nov 20, 2009 at 4:24 PM, stack st...@duboce.net wrote: Sorry, I had a bad

Asking zk cluster how its configured and whats this expired about?

2009-11-24 Thread stack
Hey lads: I want to ask a running zk cluster what its configuration is -- ticktime, session timeout, etc. -- but do not see how. There are the four letter words. Dump and stat do not print what I want. I took a look in logs -- the leader in particular -- and do not see vitals dumped out. Am

Re: Asking zk cluster how its configured and whats this expired about?

2009-11-24 Thread stack
On Tue, Nov 24, 2009 at 1:33 PM, Patrick Hunt ph...@apache.org wrote: We can definitely add this, please create a JIRA. ZOOKEEPER-595 I was also wondering what this expire stuff in the dump output is about? Those are the expiration sets, or buckets. Each client session is put into a

Re: [jira] Commented: (MAHOUT-238) Further Dependency Cleanup

2010-01-22 Thread Stack
We're working on hbase 0.21 as being the first hbase that shows up in a maven repo. St.Ack On Fri, Jan 22, 2010 at 1:12 PM, Mahadev Konar maha...@yahoo-inc.com wrote: Unfortunately no.. We are planning to deploy 3.3 as the first version on maven repo. Thanks mahadev On 1/22/10 12:58 PM,

Client seeing wrong data on nodeDataChanged

2010-10-28 Thread Stack
I'm trying to debug an issue that maybe you fellas have some ideas for figuring. In short: Client 1 updates a znode setting its content to X, then X again, then Y, and then finally it deletes the znode. Client 1 is watching the znode and I can see that its getting three nodeDataChanged events

Re: Client seeing wrong data on nodeDataChanged

2010-10-28 Thread Stack
On Thu, Oct 28, 2010 at 7:32 PM, Ted Dunning ted.dunn...@gmail.com wrote: Client 2 is not guaranteed to see X if it doesn't get to asking before the value has been updated to Y. Right, but I wouldn't expect the watch to be triggered twice with value Y. Anyways, I think we have a handle on