From 8fa33b74897742225d972b01132213c87cc1dfdc Mon Sep 17 00:00:00 2001 From: Istvan Toth Date: Fri, 6 Dec 2024 15:17:02 +0100 Subject: [PATCH] HBASE-29020 Update logging references to org.apache.hadoop.ipc in docs and examples --- 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 dea70fb200b8..3d82eb68508e 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