-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
v2 migrations should exit process on corrupt saved object document #91465
Merged
Merged
Changes from 3 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
24bc2ee
Fail migrations if a corrupt saved object is encountered
rudolf d5b7431
Merge branch 'master' into migrations-v2-corrupts-docs
kibanamachine 96fa4e8
Update test description
rudolf 61ca6cf
Merge branch 'master' into migrations-v2-corrupts-docs
rudolf 60f198f
Use an error class instead of string matching
rudolf File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -153,12 +153,27 @@ export async function migrationStateActionMachine({ | |
logger.error( | ||
logMessagePrefix + `[${e.body?.error?.type}]: ${e.body?.error?.reason ?? e.message}` | ||
); | ||
dumpExecutionLog(logger, logMessagePrefix, executionLog); | ||
throw new Error( | ||
`Unable to complete saved object migrations for the [${ | ||
initialState.indexPrefix | ||
}] index. Please check the health of your Elasticsearch cluster and try again. Error: [${ | ||
e.body?.error?.type | ||
}]: ${e.body?.error?.reason ?? e.message}` | ||
); | ||
} else { | ||
logger.error(e); | ||
|
||
dumpExecutionLog(logger, logMessagePrefix, executionLog); | ||
if (e.message.startsWith('Unable to migrate the corrupt saved object document')) { | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. NIT: I would use error sub-classing instead of relying on an error message for the handling behavior change. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. yeah I was being lazy :( |
||
throw new Error( | ||
`${e.message} To allow migrations to proceed, please delete this document from the [${initialState.indexPrefix}_${initialState.kibanaVersion}_001] index.` | ||
); | ||
} | ||
|
||
throw new Error( | ||
`Unable to complete saved object migrations for the [${initialState.indexPrefix}] index. ${e}` | ||
); | ||
} | ||
dumpExecutionLog(logger, logMessagePrefix, executionLog); | ||
throw new Error( | ||
`Unable to complete saved object migrations for the [${initialState.indexPrefix}] index. Please check the health of your Elasticsearch cluster and try again. ${e}` | ||
); | ||
} | ||
} |
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.
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.
This means that v1 migrations will also start failing on corrupt saved objects. When v1 migrations encounter a corrupt saved object it will perform a migration on every restart which can cause data loss in a multi-instance Kibana setup if only one Kibana gets restarted at a time. So although it might block some users from upgrading, deleting the saved object will save them from worse problems.
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.
Isn't this our recommended way to upgrade kibana? restarting one instance at a time
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.
No, all kibana's need to be shutdown before upgrading otherwise v1 migrations will cause data loss.
from https://www.elastic.co/guide/en/kibana/current/upgrade.html