-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Closed
Labels
:Analytics/ES|QLAKA ESQLAKA ESQL>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)medium-riskAn open issue or test failure that is a medium risk to future releasesAn open issue or test failure that is a medium risk to future releases
Description
Build Scans:
- elasticsearch-intake #28760 / part1
- elasticsearch-intake #28756 / part1
- elasticsearch-intake #28751 / part1
Reproduction Line:
./gradlew ":test:external-modules:test-esql-heap-attack:javaRestTest" --tests "org.elasticsearch.xpack.esql.heap_attack.HeapAttackIT.testLookupExplosionBigString" -Dtests.seed=4F7998AF45B554CE -Dtests.locale=luy-Latn-KE -Dtests.timezone=Asia/Sakhalin -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]:36083], 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 [530618896/506mb], 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":530618896,"bytes_limit":322122547,"durability":"TRANSIENT","stack_trace":"org.elasticsearch.common.breaker.CircuitBreakingException: [request] Data too large, data for [serialize lookup join response] would be [530618896/506mb], 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] 2 consecutive failures in test testLookupExplosionBigString
- [main] 3 consecutive failures in step part1
- [main] 3 consecutive failures in pipeline elasticsearch-intake
- [main] 3 failures in test testLookupExplosionBigString (1.3% fail rate in 225 executions)
- [main] 3 failures in step part1 (9.1% fail rate in 33 executions)
- [main] 3 failures in pipeline elasticsearch-intake (9.1% fail rate in 33 executions)
Note:
This issue was created using new test triage automation. Please report issues or feedback to es-delivery.
Metadata
Metadata
Assignees
Labels
:Analytics/ES|QLAKA ESQLAKA ESQL>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)medium-riskAn open issue or test failure that is a medium risk to future releasesAn open issue or test failure that is a medium risk to future releases