[9.1](backport #45073) Fix Elasticsearch output retry backoff when receiving 429s#45098
Merged
pierrehilbert merged 1 commit into9.1from Jul 1, 2025
Merged
[9.1](backport #45073) Fix Elasticsearch output retry backoff when receiving 429s#45098pierrehilbert merged 1 commit into9.1from
pierrehilbert merged 1 commit into9.1from
Conversation
See #36926. This fix has two components: - Return an error from `Publish` when the Elasticsearch output gets a 429 (too many requests) from Elasticsearch. This triggers a retry delay and reconnection attempt in the pipeline. - Break the backoff counters for `Publish` and `Connect` into separate values, so a successful `Connect` call (which for Elasticsearch just means that an empty http GET gave an ok response) doesn't reset the exponential backoff for bulk ingest requests when they are being throttled. (cherry picked from commit 8b25d5b)
botelastic
Bot
added
the
needs_team
6 tasks
Contributor
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
github-actions
Bot
added
bug
Team:Elastic-Agent-Data-Plane
botelastic
Bot
removed
the
needs_team
Contributor
|
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
pierrehilbert
approved these changes
Jun 29, 2025
Contributor
Author
|
This pull request has not been merged yet. Could you please review and merge it @faec? 🙏 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See #36926. This fix has two components:
Publishwhen the Elasticsearch output gets a 429 (too many requests) from Elasticsearch. This triggers a retry delay and reconnection attempt in the pipeline.PublishandConnectinto separate values, so a successfulConnectcall (which for Elasticsearch just means that an empty http GET gave an ok response) doesn't reset the exponential backoff for bulk ingest requests when they are being throttled.Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesI have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.How to test this PR locally
This comment on the issue has local testing instructions.
Related issues
This is an automatic backport of pull request Fix Elasticsearch output retry backoff when receiving 429s #45073 done by Mergify.