You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/07/12 01:31:00 UTC

[jira] [Created] (HBASE-27191) ResourceLeakDetector stacktraces can be truncated by log4j

Andrew Kyle Purtell created HBASE-27191:
-------------------------------------------

             Summary: ResourceLeakDetector stacktraces can be truncated by log4j
                 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


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]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)