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
Better handling of async processor failures #104289
Merged
joegallo
merged 14 commits into
elastic:main
from
joegallo:better-handling-of-async-processor-failures
Jan 18, 2024
Merged
Better handling of async processor failures #104289
joegallo
merged 14 commits into
elastic:main
from
joegallo:better-handling-of-async-processor-failures
Jan 18, 2024
Conversation
This file contains 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
joegallo
added
>bug
WIP
:Data Management/Ingest Node
Execution or management of Ingest Pipelines including GeoIP
Team:Data Management
Meta label for data/management team
v8.13.0
v8.12.1
v7.17.17
labels
Jan 11, 2024
If the markItemAsFailed calls happen asynchronously, then the items are recorded in the BulkRequestModifier's itemResponses ArrayList in a different order than one might otherwise expect.
I think this is faster than the original code, too, because instead of N inserts on an ArrayList that need to push items out of the way, we do a single scan through all the items.
joegallo
force-pushed
the
better-handling-of-async-processor-failures
branch
from
January 16, 2024 04:03
7ea5178
to
b01b841
Compare
Pinging @elastic/es-data-management (Team:Data Management) |
Hi @joegallo, I've created a changelog YAML for you. |
joegallo
requested review from
andreidan and
masseyke
and removed request for
andreidan
January 16, 2024 04:04
andreidan
approved these changes
Jan 18, 2024
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.
Very nice, thanks for fixing this 🚀
joegallo
added
auto-backport-and-merge
Automatically create backport pull requests and merge when ready
auto-backport
Automatically create backport pull requests when merged
v7.17.18
and removed
auto-backport-and-merge
Automatically create backport pull requests and merge when ready
v7.17.17
auto-backport
Automatically create backport pull requests when merged
labels
Jan 18, 2024
joegallo
added a commit
to joegallo/elasticsearch
that referenced
this pull request
Jan 25, 2024
joegallo
added a commit
to joegallo/elasticsearch
that referenced
this pull request
Jan 25, 2024
joegallo
added a commit
to joegallo/elasticsearch
that referenced
this pull request
Jan 25, 2024
joegallo
added a commit
that referenced
this pull request
Jan 25, 2024
joegallo
added a commit
that referenced
this pull request
Jan 25, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
>bug
:Data Management/Ingest Node
Execution or management of Ingest Pipelines including GeoIP
Team:Data Management
Meta label for data/management team
v7.17.18
v8.12.1
v8.13.0
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.
Fixes #101921
The
BulkRequestModifier
assumes itsitemResponses
are in order, but with async processors theitemResponses
can actually be in any order.itemResponses
are for recording "failures" (i.e. a processor threw an exception, a document was dropped via adrop
processor, a document was failed via afail
processor), and asynchronous failures can throw the ordering off. Each response initemResponses
tracks its own slot, however, so recreating the correct order is not difficult.