Return-Path: X-Original-To: apmail-hbase-dev-archive@www.apache.org Delivered-To: apmail-hbase-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3393899B3 for ; Thu, 26 Jan 2012 21:45:50 +0000 (UTC) Received: (qmail 28816 invoked by uid 500); 26 Jan 2012 21:45:49 -0000 Delivered-To: apmail-hbase-dev-archive@hbase.apache.org Received: (qmail 28733 invoked by uid 500); 26 Jan 2012 21:45:48 -0000 Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list dev@hbase.apache.org Received: (qmail 28725 invoked by uid 99); 26 Jan 2012 21:45:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jan 2012 21:45:48 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jdcryans@gmail.com designates 209.85.213.41 as permitted sender) Received: from [209.85.213.41] (HELO mail-yw0-f41.google.com) (209.85.213.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jan 2012 21:45:41 +0000 Received: by yhpp34 with SMTP id p34so607279yhp.14 for ; Thu, 26 Jan 2012 13:45:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=0TxywjZgKgWWn2VQHnfCmAFYfwIYFO1qvC36rsbHTF8=; b=b9VBH9iF6+eBUOPMDBj0ztwbc7QGYmXQBQTGklLoVl3W8NufcEXbSh2xNdehrkRokk VBReFjGcKR3OKDnKRZeFSeRqAvY4XPWpbRT5SWJLmPTFcwtbzAIbftfsBLHFA6uXdL2U IWuc/a8Jk4OPUCdP45ar3roTuvs8UGGRIo/lQ= MIME-Version: 1.0 Received: by 10.236.187.34 with SMTP id x22mr6301656yhm.14.1327614320300; Thu, 26 Jan 2012 13:45:20 -0800 (PST) Sender: jdcryans@gmail.com Received: by 10.101.97.18 with HTTP; Thu, 26 Jan 2012 13:45:20 -0800 (PST) In-Reply-To: <4D5F4595A9AA3746AA71BCD650058F8B01CC1A15@szxeml533-mbs.china.huawei.com> References: <4D5F4595A9AA3746AA71BCD650058F8B01CC1A15@szxeml533-mbs.china.huawei.com> Date: Thu, 26 Jan 2012 13:45:20 -0800 X-Google-Sender-Auth: mABsIwiz7eN_UWlD25kDNOQdIVQ Message-ID: Subject: Re: ANN: 0.90.6 RC1 available for download Was: 0.90.6 Release status From: Jean-Daniel Cryans To: dev@hbase.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org I deployed it on a cluster and ran some YCSB and PE, killed some servers. Also I did some local mixings with 0.90.5 to make sure it's all compatible. That's all good. The CHANGES file is wrong tho, it starts with a 0.90.7 commit and it doesn't have a release date. Not sure if it really warrants rolling out a new RC, I wonder what the others are thinking since in 0.92 we stopped updating it. Finally, 3 days might be a bit short for voting. J-D On Thu, Jan 26, 2012 at 1:40 AM, Ramakrishna s vasudevan wrote: > Hi Devs > > HBASE-0.90.6 RC1 is available for download at the following path. > > http://people.apache.org/~ramkrishna/0.90.6_RC1 > > The following defects are included in this RC > > HBASE-5196 - Failure in region split after PONR could cause region hole > HBASE-5153 - Add retry logic in HConnectionImplementation#resetZooKeeperT= rackers > > HBASE-5225 - Backport HBASE-3845 -data loss because lastSeqWritten can mi= ss memstore edits > HBASE-5235 - HLogSplitter writer thread's streams not getting closed when= any of the writer threads has exceptions. > HBASE-5237 - Addendum for HBASE-5160 and HBASE-4397 > HBASE-5269 - IllegalMonitorStateException while retryin HLog split in 0.9= 0 branch. (Induced defect in 0.90.6RC0). > > HBASE-5179 - Concurrent processing of processFaileOver and ServerShutdown= Handler may cause region to be assigned before log splitting is completed, = causing data loss > > will =A0not go into the release. =A0After good testing and confirmation i= t will be committed into future 0.90 and trunk branches. > > Unless we get any defect from the regression of this RC i would like to t= ake this RC for 0.90.6 release. > > Your suggestions are welcome. > > Please vote +1/-1 for this RC. =A0The vote closes on January 29th. > > Regards > Ram > > > > ________________________________________ > From: Ramakrishna s vasudevan > Sent: Saturday, January 21, 2012 10:08 PM > To: dev@hbase.apache.org > Subject: RE: 0.90.6 Release status > > It is always better to get in a patch with test case. =A0But if it takes = =A0a little more time to get the test case can we verify the patch with goo= d cluster testing and raise a JIRA for the test case integration that Stack= gives. > > By this way we can get the patch in the release and also satisfies Todd's= suggestion. > > Any comments so that i can raise a test task for the same. > > Regards > Ram > ________________________________________ > From: yuzhihong@gmail.com [yuzhihong@gmail.com] > Sent: Saturday, January 21, 2012 8:13 PM > To: dev@hbase.apache.org > Cc: dev@hbase.apache.org > Subject: Re: 0.90.6 Release status > > Stack said he would come up with some test for hbase-5179. > Suppose that takes a few more days, do you plan to check in the fix into = 0.90 branch ? > > According to Todd's suggestion earlier, a Jira shouldn't be open for too = long during which time patches continuously get checked in. > > Cheers > > > > On Jan 21, 2012, at 4:34 AM, Ramakrishna s vasudevan wrote: > >> Hi Devs >> >> After the first RC for 0.90.6 was taken >> HBASE-5196 - Failure in region split after PONR could cause region hole >> HBASE-5153 - Add retry logic in HConnectionImplementation#resetZooKeeper= Trackers >> >> The above 2 defects have been committed. >> >> HBASE-5179 - Concurrent processing of processFaileOver and ServerShutdow= nHandler may cause region to be assigned before log splitting is completed,= causing data loss >> HBASE-5225 - Backport HBASE-3845 -data loss because lastSeqWritten can m= iss memstore edits >> HBASE-5235 - HLogSplitter writer thread's streams not getting closed whe= n any of the writer threads has exceptions. >> HBASE-5237 - Addendum for HBASE-5160 and HBASE-4397 >> >> HBASE-5179 - is almost in a final stage for committing. =A0Thanks to Chu= nhui, Ted and Jinchao for persisting on the defect. >> >> The above defects were found during the testing for RC0. Hence i would l= ike to cut another RC once the above >> defects goes into 0.90. =A0By tomorrow 22nd January i would like to take= a release cut. >> Please let me know your suggestions/opinions. >> >> Regards >> Ram