didip opened a new issue #11592: URL: https://github.com/apache/druid/issues/11592
### Affected Version 0.21.1 ### Description After several days of smooth batch ingestion, Overlord now spins 300% consuming all of its memory even though 98% of middle managers are idle. The 5 middle managers that are running were unable to talk to Overlord via HTTP request. ``` druid.indexer.runner.type=httpRemote ``` Even after shutting down all middle managers, Overlord still spins 300%. I am dumping its heap and trying to analyze it right now. We configured Overlord to have 500 threads and 24GB heap. -- 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]
