diff --git conf/hbase-env.sh conf/hbase-env.sh
index 4ae577c..2aa723d 100644
--- conf/hbase-env.sh
+++ conf/hbase-env.sh
@@ -34,7 +34,7 @@
# Below are what we set by default. May only work with SUN JVM.
# For more on why as well as other possible settings,
# see http://wiki.apache.org/hadoop/PerformanceTuning
-export HBASE_OPTS="-ea -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode"
+export HBASE_OPTS="-ea -XX:+UseConcMarkSweepGC"
# Uncomment below to enable java garbage collection logging in the .out file.
# export HBASE_OPTS="$HBASE_OPTS -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps"
diff --git src/docbkx/performance.xml src/docbkx/performance.xml
index a54fe42..c2fffbb 100644
--- src/docbkx/performance.xml
+++ src/docbkx/performance.xml
@@ -119,7 +119,10 @@
must be explicitly enabled in HBase 0.90.x (Its defaulted to be on in
0.92.x HBase). See hbase.hregion.memstore.mslab.enabled
to true in your Configuration. See the cited
- slides for background and detail.
+ slides for background and detailThe latest jvms do better
+ regards fragmentation so make sure you are running a recent release.
+ Read down in the message,
+ Identifying concurrent mode failures caused by fragmentation..
For more information about GC logs, see .