fix: handle ElasticsearchStatusException (429) in RoutedBulkIndexer#1553
Merged
fix: handle ElasticsearchStatusException (429) in RoutedBulkIndexer#1553
Conversation
oblodgett
force-pushed
the
variant_indexer_improvements
branch
from
506a630 to
a7c467b
Compare
adamgibs
approved these changes
Apr 6, 2026
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
2 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.
The ES coordinating memory limit causes HTTP 429 rejections which throw ElasticsearchStatusException (RuntimeException). submitWithRetry only caught IOException, so 429s killed BP threads silently. Now catches ElasticsearchStatusException with sleep+backoff and requeue instead of thread death.