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 zookeeper-dev

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 addressing 13 issues (t

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

2010-03-25 Thread Stack
+1 All hbase tests pass with 3.3.0 in place. I ran small loading and nothing odd looking. Looks like no issue having a zk 3.3.0 client talk to a 3.2.2 ensemble. Requires small mods to hbase other than dropping new zk jar into hbase/lib in place of zk 3.2.2: HBASE-2380. St.Ack On Fri, Mar 19,

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

2010-03-25 Thread Stack
ssion:0x0 NIOServerCnxn: java.nio.channels.SocketChannel[connected local=/10.20.20.166:2181 remote=/10.20.20.185:60661] ... If I do stat over there I see Zookeeper version: 3.2.2-888565, built on 12/08/2009 21:51 GMT... On Thu, Mar 25, 2010 at 2:00 PM, Patrick Hunt wrote: > Stack, you can

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

2010-03-27 Thread Stack
at's just not acceptable. > > The roadmap has some detail on this, but it's out of date from our current > practices. We also need to include this information in our release notes. > http://wiki.apache.org/hadoop/ZooKeeper/Roadmap > https://issues.apache.org/jira/browse/ZOOKE

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 run manual > comma

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 November 2010 14:51,

Regards -> [VOTE] Release ZooKeeper 3.2.1 (candidate 0)]]

2009-09-03 Thread stack
(I sent below to general and private -- should have sent it to zookeeper-dev too) -- Forwarded message -- From: stack Date: Thu, Sep 3, 2009 at 1:34 PM Subject: Re: [Fwd: [Fwd: [VOTE] Release ZooKeeper 3.2.1 (candidate 0)]] To: gene...@hadoop.apache.org Cc: priv

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

2009-11-21 Thread stack (JIRA)
[ https://issues.apache.org/jira/browse/ZOOKEEPER-587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781074#action_12781074 ] stack commented on ZOOKEEPER-587: - If server changes the timeout on the client,

[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 wa