Your problem has not scaled yet to the point where you may truly get the benefit of Bigtable storage and mapreduce computations over it. Right now you have 17,000 rows. Do you intend someday to have millions or billions of them? Or do you expect your data set to not exceed a few million items?
You can try using the table split maintenance function from the shell to force splits. % hbase shell hbase> split 'mytable' but split requests are advisory and depend on having enough underlying data for the split to be sane. It is unlikely you can split a small table up over 20 region servers this way. You might be able to achieve a few forced splits, however. Hope that helps, - Andy > From: Rakhi Khatwani <[email protected]> > Subject: Re: Region Servers going down frequently > To: [email protected] > Date: Wednesday, April 8, 2009, 12:13 AM > Hi Amandeep, > > But in That case, if I let hbase split it automatically, my > table with 17000 rows will have only one region. thus my > analysis will have only one map. > won't the analysis process be slower in that case?? > > Thanks, > Raakhi
