I recently merged #72081 which protects against OOM in the reduce phase for date_histograms. A discuss user reported having a similar issue, but they seem to have it on the data nodes while building results.
Elasticsearch version (bin/elasticsearch --version): Reported on 7.9 - @nik9000 thinks it should be possible to reproduce against master
Steps to reproduce:
We just got the stack trace in the linked discuss issue. Looks like they have a wide range and tight interval. They have min_doc_count set to 0 but I don't think that matters too much here. I'd try setting one second bins a hundred thousand docs all in a different second. The trick, I think, is not to run out of memory when collecting the agg - we have protections there - but to run out of memory when building bloaty result objects we send back to the coordinating node.
I recently merged #72081 which protects against OOM in the reduce phase for date_histograms. A discuss user reported having a similar issue, but they seem to have it on the data nodes while building results.
Elasticsearch version (
bin/elasticsearch --version): Reported on 7.9 - @nik9000 thinks it should be possible to reproduce against masterSteps to reproduce:
We just got the stack trace in the linked discuss issue. Looks like they have a wide range and tight interval. They have
min_doc_countset to0but I don't think that matters too much here. I'd try setting one second bins a hundred thousand docs all in a different second. The trick, I think, is not to run out of memory when collecting the agg - we have protections there - but to run out of memory when building bloaty result objects we send back to the coordinating node.