Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 22 Nov 2017 00:52:00 +0000 (UTC)
From: "huaxiang sun (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.13120102.1511310976000.294545.1511311920148@Atlassian.JIRA>
In-Reply-To: <JIRA.13120102.1511310976000@Atlassian.JIRA>
References: <JIRA.13120102.1511310976000@Atlassian.JIRA> <JIRA.13120102.1511310976903@jira-lw-us.apache.org>
Subject: [jira] [Comment Edited] (HBASE-19320) document the mysterious
 direct memory leak in hbase
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 22 Nov 2017 00:52:05 -0000


    [ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16261779#comment-16261779 ] 

huaxiang sun edited comment on HBASE-19320 at 11/22/17 12:51 AM:
-----------------------------------------------------------------

Attach two screenshots for this issue.

The first one is query DirectByteBuffer whose capacity > 5M. The second one is the gc root path to illustrate who holds this DM. I checked all of these objects, they are have the same gc root path.

Adding these objects' capacity together, it is more than 2GB.


was (Author: huaxiang):
Attach two screenshots for this issue.

The first one is query DirectByteBuffer whose capacity > 5M. The second one is the gc root path to illustrate who holds this DM. I checked all of these objects, they are have the same gc root path.

> 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)