[
https://issues.apache.org/jira/browse/HBASE-11718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14092778#comment-14092778
]
Nicolas Liochon commented on HBASE-11718:
-----------------------------------------
> This looks like an unexpected error path – shouldn't we keep it to provide
> some indication a client is doing something fishy?
It happens with timeouts or cancellation: the client removes the callId from
its waiting list, but the server knows nothing about this. When the server
finally answers the client does not need to parse the message; so it just reads
the bytes sent.
> 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)
