Zhou, No sorry there is no guide tho I'm sure that searching through this mailing list you would find some answers.
More regions means more memory taken to manage them. 2.56MB is surely too low, try something like 128MB or even 64MB. Yes, like you saw, you also have to change the flush size if your value is very low. If using a 64MB maxsize, try using a 12MB for flushes. What is your machine setup like? (how many, what cpu, mem, hdd, etc). Thanks, J-D On Fri, Sep 26, 2008 at 8:57 AM, Zhou Wei <[EMAIL PROTECTED]>wrote: > Should I also change the value of hbase.hregion.memcache.flush.size? > > Zhou Wei > > Jean-Daniel Cryans 写道: > > Zhou, >> >> The data won't be distributed until your region passes the split threshold >> which is by default 256MB for a single family. If you really want >> distribution at your level, you should lower the >> hbase.hregion.max.filesize >> value in hbase-site.xml >> >> J-D >> >> On Fri, Sep 26, 2008 at 8:20 AM, Zhou Wei >> <[EMAIL PROTECTED]>wrote: >> >> >> >>> Hi, >>> >>> I've trying to use HBase 0.2.1 to host one table of data, about 200MB. >>> But under very high load of read and update. >>> I found out that all data is assigned to one data node, can't be scale >>> to more nodes. >>> >>> I understand that HBase is designed to store massive data. >>> Is there a way to balance the load to more data nodes? >>> >>> Thanks, >>> >>> Zhou >>> >>> >>> >> >> >> > >
