[
https://issues.apache.org/jira/browse/HBASE-27191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Kyle Purtell updated HBASE-27191:
----------------------------------------
Description:
Looks like ResourceLeakDetector stacktraces can be truncated by log4j, at least
with the default configuration. This is unfortunate because what log4j will do
then is print the first bit of the log line then only the end, which omits the
crucial top part of the stack trace.
Should these be given the NamedQueueRecorder treatment like the slow log or
balancer decisions, i.e. we would also log detected resource leaks and their
complete stacktrace details into a system table? WDYT [~vjasani] [~zhangduo]
was:
Looks like ResourceLeakDetector stacktraces can be truncated by log4j, at least
with the default configuration.
Should these be given the NamedQueueRecorder treatment like the slow log or
balancer decisions, i.e. we would also log detected resource leaks and their
complete stacktrace details into a system table? WDYT [~vjasani] [~zhangduo]
> ResourceLeakDetector stacktraces can be truncated when logged
> -------------------------------------------------------------
>
> Key: HBASE-27191
> URL: https://issues.apache.org/jira/browse/HBASE-27191
> Project: HBase
> Issue Type: Bug
> Affects Versions: 2.5.0
> Reporter: Andrew Kyle Purtell
> Priority: Minor
>
> Looks like ResourceLeakDetector stacktraces can be truncated by log4j, at
> least with the default configuration. This is unfortunate because what log4j
> will do then is print the first bit of the log line then only the end, which
> omits the crucial top part of the stack trace.
> Should these be given the NamedQueueRecorder treatment like the slow log or
> balancer decisions, i.e. we would also log detected resource leaks and their
> complete stacktrace details into a system table? WDYT [~vjasani] [~zhangduo]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
