[ https://issues.apache.org/jira/browse/HBASE-4365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13215390#comment-13215390 ]
Hadoop QA commented on HBASE-4365: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12515883/4365-v4.txt against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 3 new or modified tests. -1 javadoc. The javadoc tool appears to have generated -136 warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 153 new Findbugs (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed these unit tests: org.apache.hadoop.hbase.regionserver.TestRegionSplitPolicy Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/1038//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/1038//artifact/trunk/patchprocess/newPatchFindbugsWarnings.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/1038//console This message is automatically generated. > Add a decent heuristic for region size > -------------------------------------- > > Key: HBASE-4365 > URL: https://issues.apache.org/jira/browse/HBASE-4365 > Project: HBase > Issue Type: Improvement > Affects Versions: 0.92.1, 0.94.0 > Reporter: Todd Lipcon > Priority: Critical > Labels: usability > Attachments: 4365-v2.txt, 4365-v3.txt, 4365-v4.txt, 4365.txt > > > A few of us were brainstorming this morning about what the default region > size should be. There were a few general points made: > - in some ways it's better to be too-large than too-small, since you can > always split a table further, but you can't merge regions currently > - with HFile v2 and multithreaded compactions there are fewer reasons to > avoid very-large regions (10GB+) > - for small tables you may want a small region size just so you can > distribute load better across a cluster > - for big tables, multi-GB is probably best -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira