[ https://issues.apache.org/jira/browse/HBASE-19320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16736119#comment-16736119 ]
stack commented on HBASE-19320: ------------------------------- Thank you [~wengliemiao] for the analysis. What you suggest? Turn off use of direct memory? Change the timeout for batch pool? Should we add note to refguide? > 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: Major > 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....@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 (v7.6.3#76005)