You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by st...@apache.org on 2011/03/25 06:00:46 UTC

svn commit: r1085254 - /hbase/trunk/src/docbkx/book.xml

Author: stack
Date: Fri Mar 25 05:00:46 2011
New Revision: 1085254

URL: http://svn.apache.org/viewvc?rev=1085254&view=rev
Log:
HBASE-3622 Deadlock in HBaseServer (JVM bug?); Add an FAQ about hanging regionservers

Modified:
    hbase/trunk/src/docbkx/book.xml

Modified: hbase/trunk/src/docbkx/book.xml
URL: http://svn.apache.org/viewvc/hbase/trunk/src/docbkx/book.xml?rev=1085254&r1=1085253&r2=1085254&view=diff
==============================================================================
--- hbase/trunk/src/docbkx/book.xml (original)
+++ hbase/trunk/src/docbkx/book.xml Fri Mar 25 05:00:46 2011
@@ -959,10 +959,10 @@ When I build, why do I always get <code>
             </answer>
         </qandaentry>
     </qandadiv>
-        <qandadiv><title>Loading</title>
+        <qandadiv><title>Runtime</title>
         <qandaentry>
             <question><para>
-                    Why do I see pauses when loading HBase?
+                    Loading, why do I see pauses when loading HBase?
             </para></question>
             <answer>
                 <para>
@@ -971,6 +971,20 @@ When I build, why do I always get <code>
                 </para>
             </answer>
         </qandaentry>
+        <qandaentry>
+            <question><para>
+                    Why does my RegionServer hang inexplicitly?
+            </para></question>
+            <answer>
+                <para>
+                Are you running an old JVM (&lt; 1.6.0_u21?)?  When you look at a thread dump,
+                does it look like threads are BLOCKED but no one holds the lock all are
+                blocked on?  See <link xlink:href="https://issues.apache.org/jira/browse/HBASE-3622">HBASE 3622 Deadlock in HBaseServer (JVM bug?)</link>.
+                Adding <code>-XX:+UseMembar</code> to the HBase <varname>HBASE_OPTS</varname> in <filename>conf/hbase-env.sh</filename>
+                may fix it.
+                </para>
+            </answer>
+        </qandaentry>
     </qandadiv>
     </qandaset>
   </appendix>