+1 for the release.
Ran ant test and a couple of smoke tests. Create znodes and shutdown
zookeeper servers to test durability. Deleted znodes to make sure they are
deleted. Shot down servers one at a time to confirm correct behavior.
Thanks
mahadev
On 11/4/10 11:17 PM, Patrick Hunt
+1 based on my testing. Included testing various cluster sizes. 9
server cluster I manually verified that killing/restarting servers
worked properly, including going below majority count and then
restarting some servers. Clients maintained connectivity and recovered
sessions correctly.
LGTM.
+1.
I ran my benchmark test on the release candidate for one hour, and got
similar numbers as 3.3.0.
--Michi
On 11/10/10 11:09 AM, Mahadev Konar maha...@yahoo-inc.com wrote:
+1 for the release.
Ran ant test and a couple of smoke tests. Create znodes and shutdown
zookeeper servers to test
+1, unit tests pass. Also ran a few manual tests. I must say that in one of the computers I tried, AsyncHammerTest fails, and the error message I get is that there are no tests. Discussing with Pat, we ended up concluding that it is most likely a configuration problem. I don't think that's a
+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 he...@cloudera.com wrote:
+1
Python looks good.
On 10
With 6 +1's (3 PMC) and no -1's the vote passes. I'm working to
publish the release and will send announcements as soon as that's
done.
Patrick
On Wed, Nov 10, 2010 at 4:15 PM, Stack st...@duboce.net wrote:
+1
I put it up on a cluster under hbase and ran loads against it over
last few hours.
I've created a candidate build for ZooKeeper 3.3.2. This is a bug fix
release addressing twenty-six issues (eight critical) -- see the
release notes for details.
*** Please download, test and VOTE before the
*** vote closes 11pm pacific time, Tuesday, November 9.***
