Closed pgomulka closed 2 months ago
Pinging @elastic/es-core-infra (Team:Core/Infra)
This looks related to search hits, so passing to the search team.
Pinging @elastic/es-search (Team:Search)
I think this is the bug that @original-brownbear fixed in 8.14, but wasn't backported to 8.13. So our integration tests hit it.
Another example of this: https://gradle-enterprise.elastic.co/s/333wraumu24co/console-log?page=3
Excerpt:
[2024-06-11T13:22:55,974][ERROR][o.e.t.LeakTracker ] [v8.13.4-3] LEAK: resource was not cleaned up before it was garbage-collected.
» Recent access records:
» #1:
» org.elasticsearch.server@8.13.4/org.elasticsearch.action.search.SearchResponse.decRef(SearchResponse.java:231)
» org.elasticsearch.server@8.13.4/org.elasticsearch.action.search.MultiSearchResponse.deallocate(MultiSearchResponse.java:166)
» org.elasticsearch.server@8.13.4/org.elasticsearch.action.search.MultiSearchResponse.decRef(MultiSearchResponse.java:155)
» org.elasticsearch.server@8.13.4/org.elasticsearch.action.ActionListener.respondAndRelease(ActionListener.java:291)
» org.elasticsearch.server@8.13.4/org.elasticsearch.action.search.TransportMultiSearchAction$1.finish(TransportMultiSearchAction.java:190)
» org.elasticsearch.server@8.13.4/org.elasticsearch.action.search.TransportMultiSearchAction$1.handleResponse(TransportMultiSearchAction.java:176)
» org.elasticsearch.server@8.13.4/org.elasticsearch.action.search.TransportMultiSearchAction$1.onResponse(TransportMultiSearchAction.java:161)
» org.elasticsearch.server@8.13.4/org.elasticsearch.action.search.TransportMultiSearchAction$1.onResponse(TransportMultiSearchAction.java:157)
» org.elasticsearch.server@8.13.4/org.elasticsearch.action.ActionListener$3.onResponse(ActionListener.java:314)
@benwtrent @original-brownbear The above failure seems to occur several times per day in main and PRs. Is backporting the mentioned PR to 8.13 doable?
@rjernst https://github.com/elastic/elasticsearch/pull/108562 is backported, but since there was never an 8.13.5 release, the bugfix version of 8.13.4 doesn't have the commit.
I am not sure what to do here?
I don't know the particular test where its failing, if I did, we could just mute this particular version on this particular test.
@rjernst I will open a PR to mute all collapse
yaml tests when ran against 8.13.x.
I have muted the effected tests for < 8.14. Hopefully these failures disappear. Closing issue.
CI Link
https://gradle-enterprise.elastic.co/s/5752xbvcac4na/failure#1
Repro line
n/a
Does it reproduce?
Didn't try
Applicable branches
main 8.13.4
Failure history
No response
Failure excerpt
a mixed cluster test failed due to leak detected https://gradle-enterprise.elastic.co/s/5752xbvcac4na/failure#1