atom feed27 messages in org.apache.hadoop.hbase-devRe: hbase 0.20.0 Release Candidate 2 ...
FromSent OnAttachments
stackAug 17, 2009 10:52 pm 
Billy PearsonAug 18, 2009 8:43 am 
Jean-Daniel CryansAug 18, 2009 8:55 am 
stackAug 18, 2009 9:03 am 
Billy PearsonAug 18, 2009 10:58 am 
stackAug 18, 2009 11:46 am 
Billy PearsonAug 18, 2009 11:57 am 
Billy PearsonAug 18, 2009 12:11 pm 
stackAug 18, 2009 12:20 pm 
Andrew PurtellAug 19, 2009 6:59 am 
Andrew PurtellAug 19, 2009 8:38 am 
Tim SellAug 24, 2009 1:10 am 
Jean-Daniel CryansAug 24, 2009 7:51 am 
Jonathan GrayAug 25, 2009 4:19 pm 
Andrew PurtellAug 26, 2009 12:17 am 
Mathias HerbertsAug 26, 2009 1:03 am 
stackAug 26, 2009 7:21 am 
Andrew PurtellAug 26, 2009 8:18 am 
Jonathan GrayAug 26, 2009 9:03 am 
stackAug 26, 2009 10:44 am 
stackAug 26, 2009 11:00 am 
Ryan RawsonAug 26, 2009 11:57 am 
Jonathan GrayAug 26, 2009 12:07 pm 
Andrew PurtellAug 27, 2009 12:23 am 
Andrew PurtellAug 27, 2009 12:27 am 
stackAug 27, 2009 9:42 am 
stackAug 31, 2009 12:21 pm 
Subject:Re: hbase 0.20.0 Release Candidate 2 available for download
From:stack (sta@duboce.net)
Date:Aug 18, 2009 12:20:09 pm
List:org.apache.hadoop.hbase-dev

Thats a good one Billy. IMO, we can wait till 0.20.1 for a fix. St.Ack

On Tue, Aug 18, 2009 at 12:12 PM, Billy Pearson <sal@pearsonwholesale.com>wrote:

take a look at HBASE-1777 not sure but It might need to be addressed in 0.20.0

This cause my whole cluster to go down because each server reloads the bad column from hlog replays and the next server goes down on the next memstore flush for that region.

Billy

"stack" <sta@duboce.net> wrote in message news:7c96@mail.gmail.com...

Please file a bug Billy.

IMO this is not a critical issue since its easy enough making a workaround.

Thanks, St.Ack

On Tue, Aug 18, 2009 at 10:58 AM, Billy Pearson <sal@pearsonwholesale.com>wrote:

testing RC2

found 2009-08-18 12:54:16,572 FATAL org.apache.hadoop.hbase.regionserver.MemStoreFlusher: Replay of hlog required. Forcing server shutdown org.apache.hadoop.hbase.DroppedSnapshotException: region: webdata,http:\x2F\x2Fanaal-genomen.isporno.nl\x2F,1250569930062 at

org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:950) at org.apache.hadoop.hbase.regionserver.HRegion.flushcache(HRegion.java:843) at

org.apache.hadoop.hbase.regionserver.MemStoreFlusher.flushRegion(MemStoreFlusher.java:241) at

org.apache.hadoop.hbase.regionserver.MemStoreFlusher.run(MemStoreFlusher.java:149) Caused by: java.io.IOException: Key length 183108 > 65536 at org.apache.hadoop.hbase.io.hfile.HFile$Writer.checkKey(HFile.java:511) at org.apache.hadoop.hbase.io.hfile.HFile$Writer.append(HFile.java:479) at org.apache.hadoop.hbase.io.hfile.HFile$Writer.append(HFile.java:447) at

org.apache.hadoop.hbase.regionserver.Store.internalFlushCache(Store.java:525) at org.apache.hadoop.hbase.regionserver.Store.flushCache(Store.java:489) at

org.apache.hadoop.hbase.regionserver.HRegion.internalFlushcache(HRegion.java:935) ... 3 more

looks like from a mr job we allow keys larger then 65536 to be processed but when the memcache flush happends we kill the server should the client not fail before the long key gets in to memory?

Billy

"stack" <sta@duboce.net> wrote in message news:7c96@mail.gmail.com...

The second hbase 0.20.0 release candidate is available for download:

http://people.apache.org/~stack/hbase-0.20.0-candidate-2/<http://people.apache.org/%7Estack/hbase-0.20.0-candidate-2/> <http://people.apache.org/%7Estack/hbase-0.20.0-candidate-2/>

Near to 450 issues have been addressed since the 0.19 branch. Release notes are available here: http://su.pr/18zcEO <http://tinyurl.com/8xmyx9>.

HBase 0.20.0 runs on Hadoop 0.20.0. Alot has changed since 0.19.x including configuration fundamentals. Be sure to read the 'Getting Started' documentation in 0.20.0 available here: http://su.pr/8YQjHO

If you wish to bring your 0.19.x hbase data forward to 0.20.0, you will need to run a migration. See http://wiki.apache.org/hadoop/Hbase/HowToMigrate . First read the overview and then go to the section, 'From 0.19.x to 0.20.x'.

Should we release this candidate as hbase 0.20.0? Please vote +1/-1 by Wednesday, August 25th.

Yours, The HBasistas