[ https://issues.apache.org/jira/browse/HBASE-6185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294157#comment-13294157 ]
Hadoop QA commented on HBASE-6185: ---------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12531910/HBASE-6185.v2.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +0 tests included. The patch appears to be a documentation patch that doesn't require tests. +1 hadoop2.0. The patch compiles against the hadoop 2.0 profile. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. -1 findbugs. The patch appears to introduce 5 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.master.TestHMasterRPCException org.apache.hadoop.hbase.coprocessor.TestRegionServerCoprocessorExceptionWithAbort Test results: https://builds.apache.org/job/PreCommit-HBASE-Build/2158//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2158//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-common.html Findbugs warnings: https://builds.apache.org/job/PreCommit-HBASE-Build/2158//artifact/trunk/patchprocess/newPatchFindbugsWarningshbase-server.html Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2158//console This message is automatically generated. > Update javadoc for ConstantSizeRegionSplitPolicy class > ------------------------------------------------------ > > Key: HBASE-6185 > URL: https://issues.apache.org/jira/browse/HBASE-6185 > Project: HBase > Issue Type: Bug > Components: documentation > Affects Versions: 0.94.0 > Reporter: nneverwei > Fix For: 0.94.1 > > Attachments: HBASE-6185.patch, HBASE-6185.v2.patch > > > When using hbase0.94.0 we met a strange problem. > We config the 'hbase.hregion.max.filesize' to 100Gb (The recommed value to > act as auto-split turn off). > {code:xml} > <property> > <name>hbase.hregion.max.filesize</name> > <value>107374182400</value> > </property> > {code} > Then we keep putting datas into a table. > But when the data size far more less than 100Gb(about 500~600 uncompressed > datas), the table auto splte to 2 regions... > I change the log4j config to DEBUG, and saw logs below: > {code} > 2012-06-07 10:30:52,161 INFO org.apache.hadoop.hbase.regionserver.HRegion: > Finished memstore flush of ~128.0m/134221272, currentsize=1.5m/1617744 for > region FileStructIndex,,1339032525500.7b229abcd0785408251a579e9bdf49c8. in > 3201ms, sequenceid=176387980, compaction requested=false > 2012-06-07 10:30:52,161 DEBUG > org.apache.hadoop.hbase.regionserver.IncreasingToUpperBoundRegionSplitPolicy: > ShouldSplit because info size=138657416, sizeToCheck=134217728, > regionsWithCommonTable=1 > 2012-06-07 10:30:52,161 DEBUG > org.apache.hadoop.hbase.regionserver.IncreasingToUpperBoundRegionSplitPolicy: > ShouldSplit because info size=138657416, sizeToCheck=134217728, > regionsWithCommonTable=1 > 2012-06-07 10:30:52,240 DEBUG > org.apache.hadoop.hbase.regionserver.CompactSplitThread: Split requested for > FileStructIndex,,1339032525500.7b229abcd0785408251a579e9bdf49c8.. > compaction_queue=(0:0), split_queue=0 > 2012-06-07 10:30:52,265 INFO > org.apache.hadoop.hbase.regionserver.SplitTransaction: Starting split of > region FileStructIndex,,1339032525500.7b229abcd0785408251a579e9bdf49c8. > 2012-06-07 10:30:52,265 DEBUG > org.apache.hadoop.hbase.regionserver.SplitTransaction: > regionserver:60020-0x137c4929efe0001 Creating ephemeral node for > 7b229abcd0785408251a579e9bdf49c8 in SPLITTING state > 2012-06-07 10:30:52,368 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: > regionserver:60020-0x137c4929efe0001 Attempting to transition node > 7b229abcd0785408251a579e9bdf49c8 from RS_ZK_REGION_SPLITTING to > RS_ZK_REGION_SPLITTING > 2012-06-07 10:30:52,382 DEBUG org.apache.hadoop.hbase.zookeeper.ZKAssign: > regionserver:60020-0x137c4929efe0001 Successfully transitioned node > 7b229abcd0785408251a579e9bdf49c8 from RS_ZK_REGION_SPLITTING to > RS_ZK_REGION_SPLITTING > 2012-06-07 10:30:52,410 DEBUG org.apache.hadoop.hbase.regionserver.HRegion: > Closing FileStructIndex,,1339032525500.7b229abcd0785408251a579e9bdf49c8.: > disabling compactions & flushes > 2012-06-07 10:30:52,410 DEBUG > org.apache.hadoop.hbase.regionserver.HRegionServer: > NotServingRegionException; > FileStructIndex,,1339032525500.7b229abcd0785408251a579e9bdf49c8. is closing > 2012-06-07 10:30:52,411 DEBUG > org.apache.hadoop.hbase.regionserver.HRegionServer: > NotServingRegionException; > FileStructIndex,,1339032525500.7b229abcd0785408251a579e9bdf49c8. is closing > {code} > {color:red}IncreasingToUpperBoundRegionSplitPolicy: ShouldSplit because info > size=138657416, sizeToCheck=134217728{color} > I did not config splitPolicy for hbase, so it means > *IncreasingToUpperBoundRegionSplitPolicy is the default splitPolicy of 0.94.0* > After add > {code:xml} > <property> > <name>hbase.regionserver.region.split.policy</name> > > <value>org.apache.hadoop.hbase.regionserver.ConstantSizeRegionSplitPolicy</value> > </property> > {code} > autosplit did not happen again and everything goes well. > But we can still see javadoc on ConstantSizeRegionSplitPolicy, it says 'This > is the default split policy'. Or even in the > http://hbase.apache.org/book/regions.arch.html 9.7.4.1. Custom Split > Policies, 'default split policy: ConstantSizeRegionSplitPolicy.'. > Those may mistaken us that if we set hbase.hregion.max.filesize to 100Gb, > than the auto-split can be almost shutdown. > You may change those docs, and What more, in many scenerys, we actually need > to control split manually(As you know when spliting the table are offline, > reads and writes will fail) > -- 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