[
https://issues.apache.org/jira/browse/HBASE-22943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16919149#comment-16919149
]
Hudson commented on HBASE-22943:
--------------------------------
Results for branch master
[build #1374 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/1374/]: (x)
*{color:red}-1 overall{color}*
----
details (if available):
(/) {color:green}+1 general checks{color}
-- For more information [see general
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1374//General_Nightly_Build_Report/]
(/) {color:green}+1 jdk8 hadoop2 checks{color}
-- For more information [see jdk8 (hadoop2)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1374//JDK8_Nightly_Build_Report_(Hadoop2)/]
(x) {color:red}-1 jdk8 hadoop3 checks{color}
-- For more information [see jdk8 (hadoop3)
report|https://builds.apache.org/job/HBase%20Nightly/job/master/1374//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> 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
>
> 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)
