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:
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]>:
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:
NEW: Monitor These Apps!
Apache Lucene, Apache Solr and all other Apache Software Foundation projects and their respective logos are trademarks of the Apache Software Foundation.
Elasticsearch, Kibana, Logstash, and Beats are trademarks of Elasticsearch BV, registered in the U.S. and in other countries. This site and Sematext Group is in no way affiliated with Elasticsearch BV.
Service operated by Sematext