Just a reminder for those of you new to the community. Anyone can test
the release candidate and vote or provide feedback. We'd appreciate
you finding any issues that need to be found _now_ rather than after
the RC is released officially. It takes 3 or more +1 votes from PMC
members (and a min time of 72 biz hrs) for the release to be accepted
as the official 3.3.2 Apache ZooKeeper release.
On Wed, Nov 10, 2010 at 11:42 AM, Patrick Hunt <ph...@apache.org> wrote:
> +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.
> On Wed, Nov 10, 2010 at 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 durability. Deleted znodes to make sure they are
>> deleted. Shot down servers one at a time to confirm correct behavior.
>> On 11/4/10 11:17 PM, "Patrick Hunt" <ph...@apache.org> wrote:
>>> 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.***
>>> Should we release this?