Hi All After the RC1 release cut, few problems with CHANGES.txt was found. So i have taken a new release cut RC2 . It has an addendum for HBASE-5153 also.
Any issues found due to regression will be checked in for a new RC. Till then would like to freeze all the code changes into 0.90. Any new changes can go after the release of 0.90.6 is done. Pls vote for the new RC http://people.apache.org/~ramkrishna/0.90.6_RC2/ before February 4th. Regards Ram ________________________________________ From: Ramakrishna s vasudevan Sent: Thursday, January 26, 2012 3:10 PM To: dev@hbase.apache.org Subject: ANN: 0.90.6 RC1 available for download Was: 0.90.6 Release status 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#resetZooKeeperTrackers HBASE-5225 - Backport HBASE-3845 -data loss because lastSeqWritten can miss 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.90 branch. (Induced defect in 0.90.6RC0). HBASE-5179 - Concurrent processing of processFaileOver and ServerShutdownHandler may cause region to be assigned before log splitting is completed, causing data loss will not go into the release. After good testing and confirmation it 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 take this RC for 0.90.6 release. Your suggestions are welcome. Please vote +1/-1 for this RC. The 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. But if it takes a little more time to get the test case can we verify the patch with good 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: yuzhih...@gmail.com [yuzhih...@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 <ramkrishna.vasude...@huawei.com> 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#resetZooKeeperTrackers > > The above 2 defects have been committed. > > HBASE-5179 - Concurrent processing of processFaileOver and > ServerShutdownHandler may cause region to be assigned before log splitting is > completed, causing data loss > HBASE-5225 - Backport HBASE-3845 -data loss because lastSeqWritten can miss > 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-5179 - is almost in a final stage for committing. Thanks to Chunhui, > Ted and Jinchao for persisting on the defect. > > The above defects were found during the testing for RC0. Hence i would like > to cut another RC once the above > defects goes into 0.90. By tomorrow 22nd January i would like to take a > release cut. > Please let me know your suggestions/opinions. > > Regards > Ram
