Yeah, we learned the hard way early last year to follow the guidelines religiously. I've gone over the requirements and checked off everything. We even re-did our tables to only have 4 column families, down from 4x that amount. We are at a loss to find out why we seemed to be cursed when it comes to HBase. Hadoop is performing like a charm, pretty much every machine is busy 24/7.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stack Sent: Tuesday, May 31, 2011 3:03 PM To: [email protected] Subject: Re: wrong region exception On Tue, May 31, 2011 at 10:42 AM, Robert Gonzalez <[email protected]> wrote: > Now I'm getting the wrong region exception on the new table that I'm copying > the old table to. Running hbck reveals an inconsistency in the new table. > The frustration is unbelievable. Like I said before, it doesn't appear that > HBase is ready for prime time. I don't know how companies are using this > successfully, it doesn't appear plausible. > Sorry you are not having a good experience. I've not seen WrongRegionException in ages (Grep these lists yourself). Makes me suspect your environment. For sure you've read the requirements section in the manual and set up ulimits, nprocs and xceivers up? St.Ack
