hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-19320) document the mysterious direct memory leak in hbase
Date Wed, 22 Nov 2017 04:20:00 GMT

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

stack commented on HBASE-19320:
-------------------------------

bq, Yes, I thought this was the plan...

Its not default [1]. Filed HBASE-19323 "Make netty engine default in hbase2"

1. https://docs.google.com/document/d/1WCsVlnHjJeKUcl7wHwqb4z9iEu_ktczrlKHK8N4SZzs/edit#heading=h.hpbw1fac8ixd



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

Mime
View raw message