[Transform] Fix issue if upgrade runs right after a rolling cluster upgrade #80579
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
Collaborator
|
Pinging @elastic/ml-core (Team:ML) |
hendrikmuhs
added
the
auto-backport
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this pull request
Nov 10, 2021
…pgrade (elastic#80579) do not fail a running transform if upgrader rewrites state inbetween fixes elastic#80073
hendrikmuhs
pushed a commit
to hendrikmuhs/elasticsearch
that referenced
this pull request
Nov 10, 2021
…pgrade (elastic#80579) do not fail a running transform if upgrader rewrites state inbetween fixes elastic#80073
Collaborator
elasticsearchmachine
pushed a commit
that referenced
this pull request
Nov 10, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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.
do not fail a running transform if upgrader rewrites state inbetween
fixes #80073
Severity: This fixes a rare scenario, probably unrealistic in production: upgrade must be called directly after a rolling upgrade has finished, which is only possible if upgrade is called by automation (the issue has been triggered in CI)
Risk: medium, small change
non-issue: The upgrade endpoint has not been part of a release yet
Note: the 7.16 backport should additionally unmute 99d6a93