Reindex data stream persistent task (#116780) #117251
Merged
Conversation
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
masseyke
added
backport
:Data Management/Data streams
masseyke
changed the title
masseyke
added
the
auto-merge-without-approval
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is the shell of the persistent task to reindex a data stream. It includes the transport action that creates the persistent task, returning the persistent task id. The persistent task currently just looks up all indices for a data stream, finds the ones that need upgrading, and then marks itself as complete. The actual implementation of reindex will come later, as will the ability to call it via a rest endpoint, and the ability to fetch the status of the reindex based on the persistent task id.
Note that when the reindex task is complete, it actually schedules the persistent task to complete in 1 day. This is to allow the user (most likely the kibana upgrade assistant) up to 1 day to check the status of a reindex after it completes. Related, this means that a user must currently find and kill the task if they want to run reindex again within 1 day of a failed run. This might be improved in a future PR by using a unique persistent task id.