From 25e0f67da72a3ebadfed0ceeeb31810239b50c20 Mon Sep 17 00:00:00 2001 From: Doug Meil Date: Thu, 9 Feb 2012 19:45:06 +0000 Subject: [PATCH] hbase-5367. book.xml - minor formatting in Arch/Region/Store compaction description git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1242482 13f79535-47bb-0310-9956-ffa450edef68 --- src/docbkx/book.xml | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/src/docbkx/book.xml b/src/docbkx/book.xml index 46164d16d65..269c742676d 100644 --- a/src/docbkx/book.xml +++ b/src/docbkx/book.xml @@ -2165,15 +2165,15 @@ myHtd.setValue(HTableDescriptor.SPLIT_POLICY, MyCustomSplitPolicy.class.getName( Important knobs: hbase.store.compaction.ratio Ratio used in compaction - file selection algorithm. (default 1.2F) + file selection algorithm (default 1.2f). hbase.hstore.compaction.min (.90 hbase.hstore.compactionThreshold) (files) Minimum number - of StoreFiles per Store to be selected for a compaction to occur. - hbase.hstore.compaction.max (files) Maximum number of StoreFiles to compact per minor compaction. + of StoreFiles per Store to be selected for a compaction to occur (default 2). + hbase.hstore.compaction.max (files) Maximum number of StoreFiles to compact per minor compaction (default 10). hbase.hstore.compaction.min.size (bytes) Any StoreFile smaller than this setting with automatically be a candidate for compaction. Defaults to - regions' memstore flush size (134 mb). + hbase.hregion.memstore.flush.size (64 mb). hbase.hstore.compaction.max.size (.92) (bytes) - Any StoreFile larger than this setting with automatically be excluded from compaction. + Any StoreFile larger than this setting with automatically be excluded from compaction (default Long.MAX_VALUE). The minor compaction StoreFile selection logic is size based, and selects a file for compaction when the file @@ -2184,7 +2184,7 @@ myHtd.setValue(HTableDescriptor.SPLIT_POLICY, MyCustomSplitPolicy.class.getName( Minor Compaction File Selection - Example #1 (Basic Example) This example mirrors an example from the unit test TestCompactSelection. - hbase.store.compaction.ratio = 1.0F + hbase.store.compaction.ratio = 1.0f hbase.hstore.compaction.min = 3 (files) > hbase.hstore.compaction.max = 5 (files) > hbase.hstore.compaction.min.size = 10 (bytes) > @@ -2208,7 +2208,7 @@ myHtd.setValue(HTableDescriptor.SPLIT_POLICY, MyCustomSplitPolicy.class.getName( Minor Compaction File Selection - Example #2 (Not Enough Files To Compact) This example mirrors an example from the unit test TestCompactSelection. - hbase.store.compaction.ratio = 1.0F + hbase.store.compaction.ratio = 1.0f hbase.hstore.compaction.min = 3 (files) > hbase.hstore.compaction.max = 5 (files) > hbase.hstore.compaction.min.size = 10 (bytes) > @@ -2231,7 +2231,7 @@ myHtd.setValue(HTableDescriptor.SPLIT_POLICY, MyCustomSplitPolicy.class.getName( Minor Compaction File Selection - Example #3 (Limiting Files To Compact) This example mirrors an example from the unit test TestCompactSelection. - hbase.store.compaction.ratio = 1.0F + hbase.store.compaction.ratio = 1.0f hbase.hstore.compaction.min = 3 (files) > hbase.hstore.compaction.max = 5 (files) > hbase.hstore.compaction.min.size = 10 (bytes) > @@ -2254,13 +2254,13 @@ myHtd.setValue(HTableDescriptor.SPLIT_POLICY, MyCustomSplitPolicy.class.getName(
Impact of Key Configuration Options - hbase.store.compaction.ratio. A large ratio (e.g., 10F) will produce a single giant file. Conversely, a value of .25F will + hbase.store.compaction.ratio. A large ratio (e.g., 10) will produce a single giant file. Conversely, a value of .25 will produce behavior similar to the BigTable compaction algorithm - resulting in 4 StoreFiles. - hbase.hstore.compaction.min.size. This defaults to hbase.hregion.memstore.flush.size (134 mb). Because + hbase.hstore.compaction.min.size. Because this limit represents the "automatic include" limit for all StoreFiles smaller than this value, this value may need to be adjusted downwards in write-heavy environments where many 1 or 2 mb StoreFiles are being flushed, because every file - will be targeted for compaction, and the resulting files may still be under the min-size and require further compaction, etc. + will be targeted for compaction and the resulting files may still be under the min-size and require further compaction, etc.