You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2016/11/16 21:02:59 UTC
[jira] [Resolved] (HBASE-4633) Potential memory leak in client RPC
timeout mechanism
[ https://issues.apache.org/jira/browse/HBASE-4633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack resolved HBASE-4633.
--------------------------
Resolution: Cannot Reproduce
RPC is very different now. Resolving as cannot repro.
> Potential memory leak in client RPC timeout mechanism
> -----------------------------------------------------
>
> Key: HBASE-4633
> URL: https://issues.apache.org/jira/browse/HBASE-4633
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.90.3
> Environment: HBase version: 0.90.3 + Patches , Hadoop version: CDH3u0
> Reporter: Shrijeet Paliwal
> Attachments: HBaseclientstack.png
>
>
> Relevant Jiras: https://issues.apache.org/jira/browse/HBASE-2937,
> https://issues.apache.org/jira/browse/HBASE-4003
> We have been using the 'hbase.client.operation.timeout' knob
> introduced in 2937 for quite some time now. It helps us enforce SLA.
> We have two HBase clusters and two HBase client clusters. One of them
> is much busier than the other.
> We have seen a deterministic behavior of clients running in busy
> cluster. Their (client's) memory footprint increases consistently
> after they have been up for roughly 24 hours.
> This memory footprint almost doubles from its usual value (usual case
> == RPC timeout disabled). After much investigation nothing concrete
> came out and we had to put a hack
> which keep heap size in control even when RPC timeout is enabled. Also
> note , the same behavior is not observed in 'not so busy
> cluster.
> The patch is here : https://gist.github.com/1288023
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)