When INLINESTATS is executed, it performs a first phase where it only computes the STATS, then it stuffs the result thereof into the query plan of the second phase, which uses it to perform an InlineJoin.
The memory used for this was not properly tracked; instead we put a 1MB limit in place.
This should be properly tracked with ES|QL's circuit breaking infrastructure, otherwise many parallel INLINESTATS requests could run a node out of memory.
When INLINESTATS is executed, it performs a first phase where it only computes the
STATS, then it stuffs the result thereof into the query plan of the second phase, which uses it to perform anInlineJoin.The memory used for this was not properly tracked; instead we put a 1MB limit in place.
This should be properly tracked with ES|QL's circuit breaking infrastructure, otherwise many parallel INLINESTATS requests could run a node out of memory.