[
https://issues.apache.org/jira/browse/HBASE-13714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14650470#comment-14650470
]
Esteban Gutierrez commented on HBASE-13714:
-------------------------------------------
Correct, the call was returning a result of that size and no
BoundedByteBufferPool involved here since this is an ancient HBase 0.92 cluster.
> Add tracking of the total response queue size
> ---------------------------------------------
>
> Key: HBASE-13714
> URL: https://issues.apache.org/jira/browse/HBASE-13714
> Project: HBase
> Issue Type: Improvement
> Components: master, metrics, regionserver, rpc
> Affects Versions: 2.0.0, 1.0.2, 1.2.0
> Reporter: Esteban Gutierrez
>
> I noticed this behavior while working on HBASE-13694:
> Once we are done processing a request, we decrement the call queue size on
> the RPC server. However, responses can be very large and sometimes sending
> them can take a long time. Since we don't keep track the response queue via
> metrics it is hard to spot when the responses are using too much resources on
> the RS.
> Ideally we should be tracking on the RS how much data we have in-flight in
> the response queue via metrics and not just in the logs if the size of the
> response exceeds a threshold (e.g hbase.ipc.warn.response.size or
> hbase.ipc.warn.response.time)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
