I did some load tests on this afternoon and ran into this bug: https://issues.apache.org/jira/browse/HBASE-2964
I got this after loading only 44GB (with 1G region size), so I don't think it's that rare. I'm also running with something like 30 handlers. My tests are with 80 concurrent clients. So consider me a -0 - if no one else runs into this bug we may as well release, but it seems a step backward in stability for me from the 20100621 (the last one I did significant load testing on) -Todd On Fri, Sep 3, 2010 at 12:05 PM, Stack <[email protected]> wrote: > +1 > > Its running in production at SU. > > St.Ack > > On Mon, Aug 30, 2010 at 5:29 PM, Jean-Daniel Cryans <[email protected]> > wrote: > > BTW I'm +1, I ran the unit tests, did cluster testing with YCSB, and > > deployed it in almost all our environments here (this will be > > completed before the voting period ends). > > > > J-D > > > > On Mon, Aug 30, 2010 at 4:39 PM, Jean-Daniel Cryans <[email protected]> > wrote: > >> It's time for another DR since the new master code is about to be > >> merged in and we have a few fixes and improvements that'd beneficiate > >> from more exposure. I branched from trunk this morning and created a > >> new tag. (See http://wiki.apache.org/hadoop/Hbase/HBaseVersions for > >> more on what these 0.89.x releases are all about) > >> > >> Source binary and source tar balls are available here: > >> > >> http://people.apache.org/~jdcryans/hbase-0.89.20100830-candidate-1/ > >> > >> You can also browse the candidate documentation here: > >> > >> > http://people.apache.org/~jdcryans/hbase-0.89.20100830-candidate-1/hbase-0.89.20100830/docs/ > >> > >> Issues resolved since 0.89.20100726, our second 0.89.x release, are > >> roughly ~23 issues odd including fixed deadlocks, better handling of > >> IOEs during splits and improvements for filters: see > >> http://su.pr/2HwiUe > >> > >> Shall we release this candidate as the third in our 0.89.x series of > >> developer releases? > >> > >> Please see previous threads on 0.89 releases for more information > >> about the purpose of this release candidate - in particular, this > >> 'developer release' is for those who can tolerate risk and who are > >> willing to give feedback in advance of our next major release. We're > >> not making any guarantees that this is bug free. Its definitely not > >> for production deploys. > >> > >> We'll do another release like this in a few weeks after the new master > >> code has gone in. > >> > >> Please vote by Monday, September 6th. > >> > >> Thanks, > >> J-D > >> > > > -- Todd Lipcon Software Engineer, Cloudera
