Open carlosdelest opened 3 months ago
Pinging @elastic/es-search-foundations (Team:Search Foundations)
Just one thing to note here: the bug as seen in this stack trace has long been fixed by reading to pooled bytes arrays. We do however have a bunch of other remaining spots where we are not yet using pooled bytes.
Elasticsearch Version
7.17.x - 8.x
Installed Plugins
No response
Java Version
bundled
OS Version
N/A
Problem Description
Search responses that include a high number of hits and/or hits with considerable size can OOM a node, with the following stacktrace:
Large search responses should not OOM a node, but be cancelled.
Steps to Reproduce
This was observed in production and we don't have a reproducible script.
Logs (if relevant)
No response