-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Open
Labels
:Analytics/Compute EngineAnalytics in ES|QLAnalytics in ES|QL>test-failureTriaged test failures from CITriaged test failures from CITeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)Meta label for analytical engine team (ESQL/Aggs/Geo)low-riskAn open issue or test failure that is a low risk to future releasesAn open issue or test failure that is a low risk to future releases
Description
Build Scans:
- elasticsearch-pull-request #105691 / part-1
- elasticsearch-intake #31557 / part1
- elasticsearch-intake #31554 / part1
- elasticsearch-pull-request #105686 / part-1
- elasticsearch-pull-request #105683 / part-1
- elasticsearch-pull-request #105494 / part-1
Reproduction Line:
./gradlew ":test:external-modules:test-esql-heap-attack:javaRestTest" --tests "org.elasticsearch.xpack.esql.heap_attack.HeapAttackLookupJoinIT.testLookupExplosionBigString" -Dtests.seed=9654D79DB786CC15 -Dtests.locale=en-SH -Dtests.timezone=America/New_York -Druntime.java=25
Applicable branches:
main
Reproduces locally?:
N/A
Failure History:
See dashboard
Failure Message:
org.elasticsearch.client.ResponseException: method [POST], host [http://[::1]:34809], URI [/_query?error_trace=], status line [HTTP/1.1 429 Too Many Requests]
Warnings: [No limit defined, adding default limit of [1000]]
{"error":{"root_cause":[{"type":"circuit_breaking_exception","reason":"[request] Data too large, data for [serialize lookup join response] would be [419468576/400mb], which is larger than the limit of [322122547/307.1mb]; for more information, see https://www.elastic.co/docs/troubleshoot/elasticsearch/circuit-breaker-errors?version=master","bytes_wanted":419468576,"bytes_limit":322122547,"durability":"TRANSIENT","stack_trace":"org.elasticsearch.common.breaker.CircuitBreakingException: [request] Data too large, data for [serialize lookup join response] would be [419468576/400mb], which is larger than the limit of [322122547/307.1mb]; for more information, see https://www.elastic.co/docs/troubleshoot/elasticsearch/circuit-breaker-errors?version=master\n\tat org.elasticsea
[truncated]
Issue Reasons:
- [main] 6 failures in test testLookupExplosionBigString (35.3% fail rate in 17 executions)
- [main] 4 failures in step part-1 (36.4% fail rate in 11 executions)
- [main] 2 failures in step part1 (33.3% fail rate in 6 executions)
- [main] 4 failures in pipeline elasticsearch-pull-request (36.4% fail rate in 11 executions)
- [main] 2 failures in pipeline elasticsearch-intake (33.3% fail rate in 6 executions)
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
Metadata
Metadata
Assignees
Labels
:Analytics/Compute EngineAnalytics in ES|QLAnalytics in ES|QL>test-failureTriaged test failures from CITriaged test failures from CITeam:AnalyticsMeta label for analytical engine team (ESQL/Aggs/Geo)Meta label for analytical engine team (ESQL/Aggs/Geo)low-riskAn open issue or test failure that is a low risk to future releasesAn open issue or test failure that is a low risk to future releases