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

Posted to issues@hbase.apache.org by "Guanghao Zhang (Jira)" <ji...@apache.org> on 2019/09/03 04:06:00 UTC

[jira] [Commented] (HBASE-22943) Various procedures should not cache log trace level

    [ https://issues.apache.org/jira/browse/HBASE-22943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16921152#comment-16921152 ] 

Guanghao Zhang commented on HBASE-22943:
----------------------------------------

[~busbey] Let's close this first. And open a new issue for backport to branch-1?

> Various procedures should not cache log trace level
> ---------------------------------------------------
>
>                 Key: HBASE-22943
>                 URL: https://issues.apache.org/jira/browse/HBASE-22943
>             Project: HBase
>          Issue Type: Bug
>          Components: proc-v2
>            Reporter: Sean Busbey
>            Assignee: Sean Busbey
>            Priority: Minor
>             Fix For: 3.0.0, 2.3.0, 2.2.1, 2.1.7
>
>
> several of the procedures have an idiom where they keep a member variable for if the log is at trace level or not, wrapped in a function so that it can be lazily looked up. This gives us an overhead per call of autoboxing and a function call, instead of just the function call from asking the logging system directly.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)