You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Karthik Palanisamy (Jira)" <ji...@apache.org> on 2019/09/06 19:11:00 UTC
[jira] [Commented] (HBASE-19320) document the mysterious direct
memory leak in hbase
[ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924533#comment-16924533 ]
Karthik Palanisamy commented on HBASE-19320:
--------------------------------------------
Thanks, [~huaxiang] for the note. Users started hitting this issue, for multi-get operation. Suggested, bounding NIO temporary buffer cache.
> document the mysterious direct memory leak in hbase
> ----------------------------------------------------
>
> Key: HBASE-19320
> URL: https://issues.apache.org/jira/browse/HBASE-19320
> Project: HBase
> Issue Type: Improvement
> Affects Versions: 1.2.6, 2.0.0
> Reporter: huaxiang sun
> Assignee: huaxiang sun
> Priority: Critical
> Labels: Replication
> Attachments: HBASE-19320-master-v001.patch, Screen Shot 2017-11-21 at 4.43.36 PM.png, Screen Shot 2017-11-21 at 4.44.22 PM.png
>
>
> Recently we run into a direct memory leak case, which takes some time to trace and debug. Internally discussed with our [~saint.ack@gmail.com], we thought we had some findings and want to share with the community.
> Basically, it is the issue described in http://www.evanjones.ca/java-bytebuffer-leak.html and it happened to one of our hbase clusters.
> Create the jira first and will fill in more details later.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)