Details
-
Improvement
-
Status: Open
-
Critical
-
Resolution: Unresolved
-
1.2.6, 2.0.0
-
None
-
None
Description
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.
