Re: [Fwd: [VOTE] Release ZooKeeper 3.2.2 (candidate 0)]

2009-11-24 Thread stack
+1 Ran it in place of zk-3.2.1 in hbase context for an upload and nothing untoward examining logs. Took a quick gander at the doc. and nothing obviously amiss. St.Ack On Mon, Nov 23, 2009 at 4:53 PM, Patrick Hunt wrote: Hadoop PMC, Please test and vote on this release in

Re: [VOTE] Release ZooKeeper 3.2.2 (candidate 1)

2009-12-09 Thread stack
+1 Put it under hbase and ran a loading on a small cluster. Completed. Checked out doc. Looks right on cursory glance. St.Ack On Tue, Dec 8, 2009 at 2:32 PM, Patrick Hunt wrote: I've created a second candidate build for ZooKeeper 3.2.2. This is a bug fix release

Re: [VOTE] Release ZooKeeper 3.3.0 (candidate 0)

2010-03-27 Thread Stack
current practices. We also need to include this information in our release notes. Stack, in your specific case you are seeing that 3.3 client works fine with 3.2 server. In 3.3 we added a new

Re: [VOTE] Release ZooKeeper 3.3.1 (candidate 0)

2010-05-13 Thread Stack
+1 I installed it under hbase cluster as a 5-node ensemble. Looks like it works like 3.3.0. Did some messing sending nc commands. No prob. St.Ack On Thu, May 13, 2010 at 4:52 PM, Mahadev Konar wrote: +1. Ran ant tests and some manual testing to bring up a cluster and

Re: [VOTE] Release ZooKeeper 3.3.2 (candidate 0)

2010-11-10 Thread Stack
+1 I put it up on a cluster under hbase and ran loads against it over last few hours. Nothing untoward in logs. Played around w/ zkcli. It seems to behaving same as 3.3.1. St.Ack On Wed, Nov 10, 2010 at 3:24 PM, Henry Robinson wrote: +1 Python looks good. On 10

[jira] Commented: (ZOOKEEPER-587) client should log timeout negotiated with server

2009-11-21 Thread stack (JIRA)
[ ] stack commented on ZOOKEEPER-587: - If server changes the timeout on the client, yeah

[jira] Created: (ZOOKEEPER-595) A means of asking quorum what conifguration it is running with

2009-11-24 Thread stack (JIRA)
: Improvement Reporter: stack I'd like to ask a running quorum what its configuration is. I'd want to know stuff like session timeout and tick times. Use case is that in hbase there is no zoo.cfg usually; the configuration is manufactured and piped to the starting zk server. I want to know