This is an automated email from the ASF dual-hosted git repository.
stoty pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/hbase.git
The following commit(s) were added to refs/heads/master by this push:
new fdb0c2c782d HBASE-29020 Update logging references to
org.apache.hadoop.ipc in docs and examples (#6522)
fdb0c2c782d is described below
commit fdb0c2c782d302931cc31975c23cc0a143b07609
Author: Istvan Toth <[email protected]>
AuthorDate: Mon Dec 9 15:34:17 2024 +0100
HBASE-29020 Update logging references to org.apache.hadoop.ipc in docs and
examples (#6522)
Signed-off-by: Nihal Jain <[email protected]>
---
src/main/asciidoc/_chapters/troubleshooting.adoc | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/src/main/asciidoc/_chapters/troubleshooting.adoc
b/src/main/asciidoc/_chapters/troubleshooting.adoc
index dea70fb200b..3d82eb68508 100644
--- a/src/main/asciidoc/_chapters/troubleshooting.adoc
+++ b/src/main/asciidoc/_chapters/troubleshooting.adoc
@@ -93,11 +93,13 @@ Enabling the RPC-level logging on a RegionServer can often
give insight on timin
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` (That's
right, for `hadoop.ipc`, NOT, `hbase.ipc`). Then tail the RegionServers log.
+Set the log level to `TRACE` for the package `org.apache.hadoop.hbase.ipc`,
then tail the RegionServers log.
Analyze.
To disable, set the logging level back to `INFO` level.
+The same log settings also work on Master and for the client.
+
[[trouble.log.gc]]
=== JVM Garbage Collection Logs
