[
https://issues.apache.org/jira/browse/HBASE-27191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17566034#comment-17566034
]
Viraj Jasani commented on HBASE-27191:
--------------------------------------
+1 for making this usecase also a consumer of NamedQueue framework but I think
unlike the balancer decision/rejection case, this one would require new system
table for sure because persisting leak info would be much more helpful.
> 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)
