Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.11] [ES|QL] Force ES client timeout after 2 minutes (#168929) #169206

Merged
merged 1 commit into from
Oct 18, 2023

Conversation

kibanamachine
Copy link
Contributor

Backport

This will backport the following commits from main to 8.11:

Questions ?

Please refer to the Backport tool documentation

## Summary

We found out that for ES|QL queries while the kibana server (and
browser) timeouts in 2 minutes, the requests are still running in ES. So
instead of being aborted in 2 minutes, the hit a 5minute timeout from
the proxy which retries 3 times and then aborts.

This happens ONLY when bfetch is enabled (which is the default)

After an investigation with Rudolf it seems that we don't abort
correctly in bsearch. Lukas is fixing it here
elastic#169041 .

(cherry picked from commit 6037805)
@kibana-ci
Copy link
Collaborator

💛 Build succeeded, but was flaky

Failed CI Steps

Test Failures

  • [job] [logs] FTR Configs #23 / Endpoint plugin test metadata apis list endpoints GET route "before all" hook for "should return one entry for each host with default paging"

Metrics [docs]

✅ unchanged

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @stratoula

@kibanamachine kibanamachine merged commit c45d7d8 into elastic:8.11 Oct 18, 2023
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants