From d22a05084ae18bdf27471e6d59d86f51c9d8721c Mon Sep 17 00:00:00 2001 From: Chia-Ping Tsai Date: Sat, 9 Sep 2017 05:46:38 +0800 Subject: [PATCH] HBASE-13868 Correct "Disable automatic splitting" section in HBase book --- src/main/asciidoc/_chapters/configuration.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/main/asciidoc/_chapters/configuration.adoc b/src/main/asciidoc/_chapters/configuration.adoc index 23d1f8fbe46..423ee6bac6e 100644 --- a/src/main/asciidoc/_chapters/configuration.adoc +++ b/src/main/asciidoc/_chapters/configuration.adoc @@ -788,7 +788,7 @@ Manual splitting can mitigate region creation and movement under load. It also makes it so region boundaries are known and invariant (if you disable region splitting). If you use manual splits, it is easier doing staggered, time-based major compactions to spread out your network IO load. .Disable Automatic Splitting -To disable automatic splitting, set `hbase.hregion.max.filesize` to a very large value, such as `100 GB` It is not recommended to set it to its absolute maximum value of `Long.MAX_VALUE`. +To disable automatic splitting, you can set region split policy in either cluster configuration or table configuration to be `org.apache.hadoop.hbase.regionserver.DisabledRegionSplitPolicy` .Automatic Splitting Is Recommended [NOTE]