You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "huaxiang sun (JIRA)" <ji...@apache.org> on 2017/12/05 21:33: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=16279220#comment-16279220 ]
huaxiang sun commented on HBASE-19320:
--------------------------------------
The initial result from our testing result looks positive. We are going to update the direct memory section in hbase book accordingly after some more testing.
> 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: 2.0.0, 1.2.6
> Reporter: huaxiang sun
> Assignee: huaxiang sun
> Attachments: 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
(v6.4.14#64029)