harinirajendran opened a new issue, #12448:
URL: https://github.com/apache/druid/issues/12448

   ### Affected Version
   
   0.21, 0.22.1 [We noticed it only when we were on 0.21]. This could have been 
happening earlier too.
   
   ### Description
   95% of our real-time ingestion task logs are filled with the following 
messages
   ```
   {"@timestamp":"2022-03-28T18:30:14.181Z", "log.level": "WARN", 
"message":"Not closed! Object leaked from StupidPool{name=littleEndByteBufPool, 
objectsCacheMaxCount=2147483647, poolSize=6}. Allowing gc to prevent leak.", 
"service.name":"druid/middleManager","event.dataset":"druid/middleManager.log","process.thread.name":"Cleaner-0","log.logger":"org.apache.druid.collections.StupidPool"}
   {"@timestamp":"2022-03-28T18:30:14.181Z", "log.level": "WARN", 
"message":"Not closed! Object leaked from StupidPool{name=littleEndByteBufPool, 
objectsCacheMaxCount=2147483647, poolSize=5}. Allowing gc to prevent leak.", 
"service.name":"druid/middleManager","event.dataset":"druid/middleManager.log","process.thread.name":"Cleaner-0","log.logger":"org.apache.druid.collections.StupidPool"}
   {"@timestamp":"2022-03-28T18:30:14.181Z", "log.level": "WARN", 
"message":"Not closed! Object leaked from StupidPool{name=littleEndByteBufPool, 
objectsCacheMaxCount=2147483647, poolSize=5}. Allowing gc to prevent leak.", 
"service.name":"druid/middleManager","event.dataset":"druid/middleManager.log","process.thread.name":"Cleaner-0","log.logger":"org.apache.druid.collections.StupidPool"}
   ```
   The ingestion tasks are working fine, but the logs are flooded with these 
WARN messages.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to