HBASE-14424 Document that DisabledRegionSplitPolicy blocks manual splits

This commit is contained in:
Misty Stanley-Jones 2015-09-14 10:51:28 +10:00
parent bd9a41a368
commit 5e60166eac
2 changed files with 7 additions and 2 deletions

View File

@ -334,7 +334,8 @@ possible configurations would overwhelm and obscure the important.
<description>
A split policy determines when a region should be split. The various other split policies that
are available currently are ConstantSizeRegionSplitPolicy, DisabledRegionSplitPolicy,
DelimitedKeyPrefixRegionSplitPolicy, KeyPrefixRegionSplitPolicy etc.
DelimitedKeyPrefixRegionSplitPolicy, and KeyPrefixRegionSplitPolicy.
DisabledRegionSplitPolicy blocks manual region splitting.
</description>
</property>
<property>

View File

@ -1368,7 +1368,7 @@ The RegionServer splits a region, offlines the split region and then adds the da
See <<disable.splitting>> for how to manually manage splits (and for why you might do this).
==== Custom Split Policies
ou can override the default split policy using a custom link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/regionserver/RegionSplitPolicy.html[RegionSplitPolicy](HBase 0.94+). Typically a custom split policy should extend
You can override the default split policy using a custom link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/regionserver/RegionSplitPolicy.html[RegionSplitPolicy](HBase 0.94+). Typically a custom split policy should extend
HBase's default split policy: link:http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/regionserver/IncreasingToUpperBoundRegionSplitPolicy.html[IncreasingToUpperBoundRegionSplitPolicy].
The policy can set globally through the HBase configuration or on a per-table
@ -1407,6 +1407,8 @@ HTableDescriptor myHtd = ...;
myHtd.setValue(HTableDescriptor.SPLIT_POLICY, MyCustomSplitPolicy.class.getName());
----
NOTE: The `DisabledRegionSplitPolicy` policy blocks manual region splitting.
[[manual_region_splitting_decisions]]
=== Manual Region Splitting
@ -1426,6 +1428,8 @@ There may be other valid reasons, but the need to manually split your table migh
See <<disable.splitting>> for a discussion about the dangers and possible benefits of managing splitting completely manually.
NOTE: The `DisabledRegionSplitPolicy` policy blocks manual region splitting.
==== Determining Split Points
The goal of splitting your table manually is to improve the chances of balancing the load across the cluster in situations where good rowkey design alone won't get you there.