hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ramkrishna.s.vasudevan (JIRA)" <j...@apache.org>
Subject [jira] [Created] (HBASE-16635) RpcClient under heave load leaks some netty bytebuf
Date Thu, 15 Sep 2016 04:44:20 GMT
ramkrishna.s.vasudevan created HBASE-16635:

             Summary: RpcClient under heave load leaks some netty bytebuf
                 Key: HBASE-16635
                 URL: https://issues.apache.org/jira/browse/HBASE-16635
             Project: HBase
          Issue Type: Bug
            Reporter: ramkrishna.s.vasudevan
            Assignee: ramkrishna.s.vasudevan
            Priority: Minor
             Fix For: 2.0.0

Yet to analyse the actual root cause. 
But the case is that when we run a PE tool with 50 threads under heavy load when the writes
are clogged I think we have some netty Bytebuf leak. Not sure if it is a serious issue but
we get this log
2016-09-14 19:37:09,767 ERROR [Default-IPC-NioEventLoopGroup-1-16] util.ResourceLeakDetector:
LEAK: ByteBuf.release() was not called before it's garbage-collected. Enable advanced leak
reporting to find out where the leak occurred. To enable advanced leak reporting, specify
the JVM option '-Dio.netty.leakDetection.level=advanced' or call ResourceLeakDetector.setLevel()
See http://netty.io/wiki/reference-counted-objects.html for more information.
So reading the given link it is because of some ByteBuf that was not released properly by
the client and hence it gets GCed automatically. Netty provides tips and tricks to find the
root cause. Will get back here.

This message was sent by Atlassian JIRA

View raw message