Skip to content

[8.x] Avoid updating settings version in MetadataMigrateToDataStreamService when settings have not changed (#118704) #118706

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

Merged
merged 1 commit into from
Dec 13, 2024

Conversation

masseyke
Copy link
Member

Backports the following commits to 8.x:

… when settings have not changed (elastic#118704)

If the input index already has the `index.hidden` setting set to `true`,
MetadataMigrateToDataStreamService::prepareBackingIndex can incorrectly
increment the settings version even if it does not change the settings.
This results in an assertion failure in IndexService::updateMetadata
that will take down a node if assertions are enabled. This fixes that,
only incrementing the settings version if the settings actually changed.
@masseyke masseyke added :Data Management/Data streams Data streams and their lifecycles >bug auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport Team:Data Management Meta label for data/management team labels Dec 13, 2024
@elasticsearchmachine elasticsearchmachine merged commit ee0bb73 into elastic:8.x Dec 13, 2024
15 checks passed
@masseyke masseyke deleted the backport/8.x/pr-118704 branch December 13, 2024 23:35
maxhniebergall pushed a commit to maxhniebergall/elasticsearch that referenced this pull request Dec 16, 2024
… when settings have not changed (elastic#118704) (elastic#118706)

If the input index already has the `index.hidden` setting set to `true`,
MetadataMigrateToDataStreamService::prepareBackingIndex can incorrectly
increment the settings version even if it does not change the settings.
This results in an assertion failure in IndexService::updateMetadata
that will take down a node if assertions are enabled. This fixes that,
only incrementing the settings version if the settings actually changed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-merge-without-approval Automatically merge pull request when CI checks pass (NB doesn't wait for reviews!) backport >bug :Data Management/Data streams Data streams and their lifecycles Team:Data Management Meta label for data/management team v8.18.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants