Apache
/
hbase
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

HBASE-4164 - moved loglevel note in Performance to Troubleshooting with rest of log info. 

git-svn-id: https://svn.apache.org/repos/asf/hbase/trunk@1153856 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Doug Meil 2011-08-04 12:05:51 +00:00
parent e389495ac9
commit fc48eb8336
2 changed files with 17 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
src/docbkx/performance.xml
View File

@ -9,20 +9,6 @@
xmlns:db="http://docbook.org/ns/docbook"> xmlns:db="http://docbook.org/ns/docbook">
<title>Performance Tuning</title> <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"> <section xml:id="perf.os">
<title>Operating System</title> <title>Operating System</title>
<section xml:id="perf.os.ram"> <section xml:id="perf.os.ram">

19
src/docbkx/troubleshooting.xml
View File

@ -77,8 +77,23 @@
<title>DataNode</title> <title>DataNode</title>
<para>Each DataNode server will have a DataNode log for HDFS, as well as a RegionServer log for HBase.</para> <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> <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"> <section xml:id="trouble.log.gc">
<title>JVM Garbage Collection Logs</title> <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". <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".