Bryan Beaudreault created HBASE-27953:
-----------------------------------------

             Summary: Leak in ServerCall.setResponse
                 Key: HBASE-27953
                 URL: https://issues.apache.org/jira/browse/HBASE-27953
             Project: HBase
          Issue Type: Bug
            Reporter: Bryan Beaudreault


I'm stress testing the RegionServer for TLS and noticing the following leak:

 
{code:java}
ERROR org.apache.hbase.thirdparty.io.netty.util.ResourceLeakDetector: LEAK: 
RefCnt.release() was not called before it's garbage-collected. See 
https://netty.io/wiki/reference-counted-objects.html for more information.
Recent access records:
Created at:
        org.apache.hadoop.hbase.nio.RefCnt.<init>(RefCnt.java:59)
        
org.apache.hadoop.hbase.nio.SingleByteBuff.<init>(SingleByteBuff.java:55)
        
org.apache.hadoop.hbase.io.ByteBuffAllocator.allocateOneBuffer(ByteBuffAllocator.java:280)
        
org.apache.hadoop.hbase.io.ByteBufferListOutputStream.allocateNewBuffer(ByteBufferListOutputStream.java:61)
        
org.apache.hadoop.hbase.io.ByteBufferListOutputStream.checkSizeAndGrow(ByteBufferListOutputStream.java:90)
        
org.apache.hadoop.hbase.io.ByteBufferOutputStream.writeInt(ByteBufferOutputStream.java:154)
        
org.apache.hadoop.hbase.util.ByteBufferUtils.putInt(ByteBufferUtils.java:429)
        
org.apache.hadoop.hbase.codec.KeyValueCodec$KeyValueEncoder.write(KeyValueCodec.java:61)
        
org.apache.hadoop.hbase.ipc.CellBlockBuilder.encodeCellsTo(CellBlockBuilder.java:187)
        
org.apache.hadoop.hbase.ipc.CellBlockBuilder.buildCellBlockStream(CellBlockBuilder.java:223)
        org.apache.hadoop.hbase.ipc.ServerCall.setResponse(ServerCall.java:256)
        org.apache.hadoop.hbase.ipc.CallRunner.run(CallRunner.java:160)
        
org.apache.hadoop.hbase.ipc.CallRunnerWithContext.run(CallRunnerWithContext.java:74)
        org.apache.hadoop.hbase.ipc.RpcHandler.run(RpcHandler.java:102)
        org.apache.hadoop.hbase.ipc.RpcHandler.run(RpcHandler.java:82) {code}
 

One thing to note is that due to my stress test Netty is throwing 
OutOfDirectMemoryError, which extends OutOfMemoryError. I see we have handling 
for that in CallRunner, not sure if it's related.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to