[
https://issues.apache.org/jira/browse/HBASE-11718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14092865#comment-14092865
]
Nicolas Liochon commented on HBASE-11718:
-----------------------------------------
bq. so it still sounds like a relatively rare case that won't pollute the logs.
If you're using the replica, it will pollute the logs (depending of the timeout
set. But for most configs, you will have multiple messages per second: 2 thirds
of the messages sent with replicas will be canceled. If you set the timeout at
95% percentile, ~2% of the client queries will log the message...
> Remove some logs in RpcClient.java
> ----------------------------------
>
> Key: HBASE-11718
> URL: https://issues.apache.org/jira/browse/HBASE-11718
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 1.0.0, 2.0.0
> Reporter: Nicolas Liochon
> Assignee: Nicolas Liochon
> Fix For: 1.0.0, 2.0.0
>
> Attachments: 11718.v1.patch
>
>
> All the debug level logs there are about connection start/stop, except a few
> that are per request. As a result, we log too much when we're at the debug
> log level. It could be changed to "trace", but when you're at the trace level
> you usually end up with a debugger to have all the info you need, so I think
> it's better to remove them.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
