Return-Path: Delivered-To: apmail-hadoop-zookeeper-user-archive@minotaur.apache.org Received: (qmail 36125 invoked from network); 3 Feb 2010 17:51:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 3 Feb 2010 17:51:05 -0000 Received: (qmail 99988 invoked by uid 500); 3 Feb 2010 17:51:05 -0000 Delivered-To: apmail-hadoop-zookeeper-user-archive@hadoop.apache.org Received: (qmail 99867 invoked by uid 500); 3 Feb 2010 17:51:04 -0000 Mailing-List: contact zookeeper-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: zookeeper-user@hadoop.apache.org Delivered-To: mailing list zookeeper-user@hadoop.apache.org Received: (qmail 99790 invoked by uid 99); 3 Feb 2010 17:51:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Feb 2010 17:51:04 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [216.145.54.172] (HELO mrout2.yahoo.com) (216.145.54.172) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Feb 2010 17:50:56 +0000 Received: from [10.73.135.250] (wifi-e-135-250.corp.yahoo.com [10.73.135.250]) by mrout2.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id o13HoAP8058619; Wed, 3 Feb 2010 09:50:11 -0800 (PST) Message-ID: <4B69B753.2050603@apache.org> Date: Wed, 03 Feb 2010 09:50:11 -0800 From: Patrick Hunt User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: zookeeper-dev@hadoop.apache.org CC: zookeeper-user Subject: Re: ZOOKEEPER-22 and release 3.3 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org While this is a very useful improvement it sounds to me like the prudent thing to do given the short time to 3.3.0. If you want we can shoot for 3.4.0 soon after 3.3.0 goes out (with 22 as one of the primary features). Patrick Mahadev Konar wrote: > Hi all, > > I had been working on zookeeper-22 and found out that it needs quite a few > extensive changes. We will need to do some memory measurements to see if it > has any memory impacts or not. > > Since we are targetting 3.3 release for early march, ZOOKEEPER-22 would be > hard to get into 3.3. I am proposing to move it to a later release (3.4), so > that it can be tested early in the release phase and gets baked in the > release. > > > Thanks > mahadev >