Index: pom.xml =================================================================== --- pom.xml (revision 1459011) +++ pom.xml (working copy) @@ -696,7 +696,7 @@ org.codehaus.mojo xml-maven-plugin - 1.0-beta-3 + 1.0 false @@ -710,12 +710,12 @@ - ${basedir}/hbase-server/src/main/resources/ + ${basedir}/hbase-common/src/main/resources/ hbase-default.xml ${basedir}/src/xslt/configuration_to_docbook_section.xsl - ${basedir}/target/site + ${basedir}/target/docbkx Index: src/docbkx/configuration.xml =================================================================== --- src/docbkx/configuration.xml (revision 1459011) +++ src/docbkx/configuration.xml (working copy) @@ -668,8 +668,8 @@ the build of the hbase site. See the hbase pom.xml. The generated file is a docbook section with a glossary in it--> - + +
@@ -1027,7 +1027,7 @@ Typically you want to keep your region count low on HBase for numerous reasons. Usually right around 100 regions per RegionServer has yielded the best results. Here are some of the reasons below for keeping region count low: - + MSLAB requires 2mb per memstore (that's 2mb per family per region). 1000 regions that have 2 families each is 3.9GB of heap used, and it's not even storing data yet. NB: the 2MB value is configurable. @@ -1063,7 +1063,7 @@ on a few RS can cause the store file index to rise raising heap usage and can create memory pressure or OOME on the RSs - + Another issue is the effect of the number of regions on mapreduce jobs. Keeping 5 regions per RS would be too low for a job, whereas 1000 will generate too many maps.