From fc48eb8336b1db6acbaa4a91b7ef48e0617824ac Mon Sep 17 00:00:00 2001
From: Doug Meil <dmeil@apache.org>
Date: Thu, 4 Aug 2011 12:05:51 +0000
Subject: [PATCH] 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
---
 src/docbkx/performance.xml     | 14 --------------
 src/docbkx/troubleshooting.xml | 19 +++++++++++++++++--
 2 files changed, 17 insertions(+), 16 deletions(-)

diff --git a/src/docbkx/performance.xml b/src/docbkx/performance.xml
index 175297af613..d03e632b9cd 100644
--- a/src/docbkx/performance.xml
+++ b/src/docbkx/performance.xml
@@ -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">
diff --git a/src/docbkx/troubleshooting.xml b/src/docbkx/troubleshooting.xml
index a42aa266791..9f93cd92f19 100644
--- a/src/docbkx/troubleshooting.xml
+++ b/src/docbkx/troubleshooting.xml
@@ -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".