Hi Jean-Marc, Thanks. It's ok now. I thought I had run major_compact from shell but maybe the effect was not immediate.
/David On Tue, Feb 11, 2014 at 12:17 AM, Jean-Marc Spaggiari < [email protected]> wrote: > Hi David, > > If I'm correct, that will take action only when something will be written > in the region. If you are only reading from the region, even if it's 500mb, > and even if you have setup the max size to 64MB, there will be no split. > > If you do a compaction of the region it will split. > > If you want to all spit small, just to a major_compact using HBase shell. > > JM > > > 2014-02-10 18:07 GMT-05:00 Ted Yu <[email protected]>: > > > See the following usage: > > > > For example, to change the max size of a family to 128MB, do: > > > > hbase> alter 't1', METHOD => 'table_att', *MAX_FILESIZE* => '134217728' > > > > > > On Mon, Feb 10, 2014 at 3:03 PM, David Koch <[email protected]> > wrote: > > > > > Hi, > > > > > > I reduced the MAX_FILE_SIZE to 64mb on an existing HBase table to force > > > more regions. However, it seems that this limit is not respected by > > quite a > > > large number of regions. I find several regions of >500mb size. I > checked > > > this by doing: > > > > > > hadoop fs -ls -h /hbase/<my_table>/*/<my_col_fam> > > > > > > What can be done to force re-sizing? > > > > > > Thanks, > > > > > > David > > > > > >
