[
https://issues.apache.org/jira/browse/HBASE-20780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16523750#comment-16523750
]
Hudson commented on HBASE-20780:
--------------------------------
Results for branch master
[build #377 on
builds.a.o|https://builds.apache.org/job/HBase%20Nightly/job/master/377/]: (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/377//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/377//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/377//JDK8_Nightly_Build_Report_(Hadoop3)/]
(/) {color:green}+1 source release artifact{color}
-- See build output for details.
(/) {color:green}+1 client integration test{color}
> ServerRpcConnection logging cleanup
> -----------------------------------
>
> Key: HBASE-20780
> URL: https://issues.apache.org/jira/browse/HBASE-20780
> Project: HBase
> Issue Type: Sub-task
> Components: logging, Performance
> Reporter: stack
> Assignee: stack
> Priority: Major
> Fix For: 3.0.0, 2.1.0, 2.0.2
>
> Attachments: 2.0621.2.12782.lock.svg, 2.0621.2M.46340.lock.svg,
> 2.0623.111354.lock.svg, HBASE-20780.branch-2.0.001.patch,
> HBASE-20780.branch-2.0.001.patch
>
>
> The logging we do inside in connection header parsing shows as worst offender
> in the perf locking profiles. Its odd, but easy to clean up. I'd doubt it
> makes any difference in throughput but lets get it out of the way. Let me
> load up a few samples of what it current looks like.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
