Bump major version for feature migration system indices#117243
Merged
jfreden merged 4 commits intoelastic:mainfrom Nov 22, 2024
Merged
Bump major version for feature migration system indices#117243jfreden merged 4 commits intoelastic:mainfrom
jfreden merged 4 commits intoelastic:mainfrom
Conversation
Contributor
Author
|
Created this instead of the original PR since this needs to be created against main and backported. |
Collaborator
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
Collaborator
|
Hi @jfreden, I've created a changelog YAML for you. |
gwbrown
approved these changes
Nov 21, 2024
Collaborator
💔 Backport failed
You can use sqren/backport to manually backport by running |
Contributor
Author
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
jfreden
added a commit
to jfreden/elasticsearch
that referenced
this pull request
Nov 22, 2024
* Bump major version for feature upgrade system indices (cherry picked from commit 546e8e9) # Conflicts: # server/src/main/java/org/elasticsearch/action/admin/cluster/migration/TransportGetFeatureUpgradeStatusAction.java
smalyshev
pushed a commit
to smalyshev/elasticsearch
that referenced
this pull request
Nov 22, 2024
* Bump major version for feature upgrade system indices
alexey-ivanov-es
pushed a commit
to alexey-ivanov-es/elasticsearch
that referenced
this pull request
Nov 28, 2024
* Bump major version for feature upgrade system indices
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR is in preparation for the ES 9 release. Lucene has BWC with indices created on one version prior to the current version (ES 9.0 is Lucene 10, so can support Lucene 9). To ensure that a system index created on an ES 7 (Lucene 8) can actually run on ES 9 (Lucene 10), the system indices need to be reindexed.
To reindex a system index for ES 9, the cluster need to be ugraded to
8.latestand then run the Kibana Upgrade Assistant or use the Feature MIgration APIs directly. The feature migration APIs enable you to see what features require changes, initiate the automatic migration process, and check migration status.For system indices to show up as "needs upgrade" in the
GET /_migration/system_featuresthe minimum index and stack version need to be bumped from 7 to 8. The suffix added to migrated indices also need to use version 9.