diff --git a/src/main/docbkx/book.xml b/src/main/docbkx/book.xml index dbf580cfcad..35b78483555 100644 --- a/src/main/docbkx/book.xml +++ b/src/main/docbkx/book.xml @@ -3205,7 +3205,7 @@ myHtd.setValue(HTableDescriptor.SPLIT_POLICY, MyCustomSplitPolicy.class.getName( - +
Parameters Used by Compaction Algorithm This table contains the main configuration parameters for compaction. This diff --git a/src/main/docbkx/configuration.xml b/src/main/docbkx/configuration.xml index 1d257b95f81..9a42c606a88 100644 --- a/src/main/docbkx/configuration.xml +++ b/src/main/docbkx/configuration.xml @@ -1387,14 +1387,19 @@ index e70ebc6..96f8c27 100644
Managed Compactions - A common administrative technique is to manage major compactions manually, rather than - letting HBase do it. By default, HConstants.MAJOR_COMPACTION_PERIOD is - one day and major compactions may kick in when you least desire it - especially on a busy - system. To turn off automatic major compactions set the value to 0. - It is important to stress that major compactions are absolutely necessary for - StoreFile cleanup, the only variant is when they occur. They can be administered through - the HBase shell, or via HBaseAdmin. + By default, major compactions are scheduled to run once in a 7-day period. Prior to HBase 0.96.x, major + compactions were scheduled to happen once per day by default. + If you need to control exactly when and how often major compaction runs, you can + disable managed major compactions. See the entry for + hbase.hregion.majorcompaction in the table for details. + + Do Not Disable Major Compactions + Major compactions are absolutely necessary for StoreFile clean-up. Do not disable + them altogether. You can run major compactions manually via the HBase shell or via the HBaseAdmin + API. + For more information about compactions and the compaction file selection process, see