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/06/11 20:55:00 UTC

[jira] [Resolved] (HBASE-12061) Ensure LOG.isXXXEnabled() wrapper around LOG.XXX() calls

     [ https://issues.apache.org/jira/browse/HBASE-12061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Kyle Purtell resolved HBASE-12061.
-----------------------------------------
      Assignee:     (was: Vladimir Rodionov)
    Resolution: Abandoned

> Ensure LOG.isXXXEnabled() wrapper around LOG.XXX() calls
> --------------------------------------------------------
>
>                 Key: HBASE-12061
>                 URL: https://issues.apache.org/jira/browse/HBASE-12061
>             Project: HBase
>          Issue Type: Sub-task
>          Components: Performance
>            Reporter: Vladimir Rodionov
>            Priority: Major
>
> The common anti-pattern in Java is using LOG.xxx() calls w/o wrapping them into LOG.isXXXEnabled(). This results in unnecessary object serializations/ string concatenations/ garbage object production even if XXX log level is disabled.   



--
This message was sent by Atlassian Jira
(v8.20.7#820007)