[
https://issues.apache.org/jira/browse/HBASE-20780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack updated HBASE-20780:
--------------------------
Resolution: Fixed
Fix Version/s: 2.0.2
2.1.0
3.0.0
Status: Resolved (was: Patch Available)
Pushed logging change to branch-2.0+
> 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)
