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.
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
Add retry to bulk indexer #39
Add retry to bulk indexer #39
Changes from 1 commit
2bf0954
524b0aa
4d70896
5049818
afd66d9
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMO fallback should be added here too, exponential is a good candidate for 3 retries
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@artem-shelkovnikov I've added a temporary fallback; if a bulk index fails, it saves the failed payload to a file and outputs that file name to the log. Users can cross reference the file content with whatever error response they received.
In the future I'd like to implement something else, but for now I think this should suffice.
I also added exponentially increasing wait times for the retries.
Now, in testing this, I realised the bulk queue can get overloaded if it encounters a lot of errors and exponentially backs off for many seconds. The crawler continues to try sending crawl results and the bulk indexer trips over itself and chaos.
I have an idea to fix this but I think it's out of scope for this PR, so I'll do it in a follow-up PR.