You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by dm...@apache.org on 2011/08/04 14:05:52 UTC
svn commit: r1153856 - in /hbase/trunk/src/docbkx: performance.xml
troubleshooting.xml
Author: dmeil
Date: Thu Aug 4 12:05:51 2011
New Revision: 1153856
URL: http://svn.apache.org/viewvc?rev=1153856&view=rev
Log:
HBASE-4164 - moved loglevel note in Performance to Troubleshooting with rest of log info.
Modified:
hbase/trunk/src/docbkx/performance.xml
hbase/trunk/src/docbkx/troubleshooting.xml
Modified: hbase/trunk/src/docbkx/performance.xml
URL: http://svn.apache.org/viewvc/hbase/trunk/src/docbkx/performance.xml?rev=1153856&r1=1153855&r2=1153856&view=diff
==============================================================================
--- hbase/trunk/src/docbkx/performance.xml (original)
+++ hbase/trunk/src/docbkx/performance.xml Thu Aug 4 12:05:51 2011
@@ -9,20 +9,6 @@
xmlns:db="http://docbook.org/ns/docbook">
<title>Performance Tuning</title>
- <note xml:id="rpc.logging"><title>Enabling RPC-level logging</title>
- <para>Enabling the RPC-level logging on a RegionServer can often given
- insight on timings at the server. Once enabled, the amount of log
- spewed is voluminous. It is not recommended that you leave this
- logging on for more than short bursts of time. To enable RPC-level
- logging, browse to the RegionServer UI and click on
- <emphasis>Log Level</emphasis>. Set the log level to <varname>DEBUG</varname> for the package
- <classname>org.apache.hadoop.ipc</classname> (Thats right, for
- hadoop.ipc, NOT, hbase.ipc). Then tail the RegionServers log.
- Analyze.</para>
- <para>To disable, set the logging level back to <varname>INFO</varname> level.
- </para>
- </note>
-
<section xml:id="perf.os">
<title>Operating System</title>
<section xml:id="perf.os.ram">
Modified: hbase/trunk/src/docbkx/troubleshooting.xml
URL: http://svn.apache.org/viewvc/hbase/trunk/src/docbkx/troubleshooting.xml?rev=1153856&r1=1153855&r2=1153856&view=diff
==============================================================================
--- hbase/trunk/src/docbkx/troubleshooting.xml (original)
+++ hbase/trunk/src/docbkx/troubleshooting.xml Thu Aug 4 12:05:51 2011
@@ -77,8 +77,23 @@
<title>DataNode</title>
<para>Each DataNode server will have a DataNode log for HDFS, as well as a RegionServer log for HBase.</para>
<para>Additionally, each DataNode server will also have a TaskTracker log for MapReduce task execution.</para>
- </section>
- </section>
+ </section>
+ </section>
+ <section xml:id="trouble.log.levels">
+ <title>Log Levels</title>
+ <section xml:id="rpc.logging"><title>Enabling RPC-level logging</title>
+ <para>Enabling the RPC-level logging on a RegionServer can often given
+ insight on timings at the server. Once enabled, the amount of log
+ spewed is voluminous. It is not recommended that you leave this
+ logging on for more than short bursts of time. To enable RPC-level
+ logging, browse to the RegionServer UI and click on
+ <emphasis>Log Level</emphasis>. Set the log level to <varname>DEBUG</varname> for the package
+ <classname>org.apache.hadoop.ipc</classname> (Thats right, for
+ <classname>hadoop.ipc</classname>, NOT, <classname>hbase.ipc</classname>). Then tail the RegionServers log. Analyze.</para>
+ <para>To disable, set the logging level back to <varname>INFO</varname> level.
+ </para>
+ </section>
+ </section>
<section xml:id="trouble.log.gc">
<title>JVM Garbage Collection Logs</title>
<para>HBase is memory intensive, and using the default GC you can see long pauses in all threads including the <emphasis>Juliet Pause</emphasis> aka "GC of Death".