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"> Performance Tuning - Enabling RPC-level logging - 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 - Log Level. Set the log level to DEBUG for the package - org.apache.hadoop.ipc (Thats right, for - hadoop.ipc, NOT, hbase.ipc). Then tail the RegionServers log. - Analyze. - To disable, set the logging level back to INFO level. - - -
Operating System
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 @@ DataNode Each DataNode server will have a DataNode log for HDFS, as well as a RegionServer log for HBase. Additionally, each DataNode server will also have a TaskTracker log for MapReduce task execution. -
-
+ + +
+ Log Levels +
Enabling RPC-level logging + 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 + Log Level. Set the log level to DEBUG for the package + org.apache.hadoop.ipc (Thats right, for + hadoop.ipc, NOT, hbase.ipc). Then tail the RegionServers log. Analyze. + To disable, set the logging level back to INFO level. + +
+
JVM Garbage Collection Logs HBase is memory intensive, and using the default GC you can see long pauses in all threads including the Juliet Pause aka "GC of Death".