-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[ML] Error creating annotations index after upgrading 6.x -> 7.x -> 8.x #82250
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
Comments
Pinging @elastic/ml-core (Team:ML) |
droberts195
added a commit
to droberts195/elasticsearch
that referenced
this issue
Jan 6, 2022
The code that manages the ML annotations index was not taking into account the possibility that the usual index name would be an alias pointing to a reindexed copy of the index. This is exactly what happens when the upgrade assistant reindexes indices into the latest Lucene format. Fixes elastic#82250
droberts195
added a commit
that referenced
this issue
Jan 6, 2022
The code that manages the ML annotations index was not taking into account the possibility that the usual index name would be an alias pointing to a reindexed copy of the index. This is exactly what happens when the upgrade assistant reindexes indices into the latest Lucene format. Fixes #82250
droberts195
added a commit
to droberts195/elasticsearch
that referenced
this issue
Jan 6, 2022
The code that manages the ML annotations index was not taking into account the possibility that the usual index name would be an alias pointing to a reindexed copy of the index. This is exactly what happens when the upgrade assistant reindexes indices into the latest Lucene format. Fixes elastic#82250
elasticsearchmachine
pushed a commit
that referenced
this issue
Jan 6, 2022
) The code that manages the ML annotations index was not taking into account the possibility that the usual index name would be an alias pointing to a reindexed copy of the index. This is exactly what happens when the upgrade assistant reindexes indices into the latest Lucene format. Fixes #82250
astefan
pushed a commit
to astefan/elasticsearch
that referenced
this issue
Jan 7, 2022
The code that manages the ML annotations index was not taking into account the possibility that the usual index name would be an alias pointing to a reindexed copy of the index. This is exactly what happens when the upgrade assistant reindexes indices into the latest Lucene format. Fixes elastic#82250
astefan
pushed a commit
to astefan/elasticsearch
that referenced
this issue
Jan 7, 2022
The code that manages the ML annotations index was not taking into account the possibility that the usual index name would be an alias pointing to a reindexed copy of the index. This is exactly what happens when the upgrade assistant reindexes indices into the latest Lucene format. Fixes elastic#82250
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following error was seen after upgrading a cluster where ML was in use from 6.8 to 7.17, reindexing indices as suggested by the upgrade assistant, then upgrading to 8.1:
This error implies there's a bug in the ML annotations index code when
.ml-annotations-6
is an alias rather than a concrete index. That name becomes an alias when the index is reindexed into the 7.x Lucene index format so that it's still readable in 8.x. The concrete index is then.reindexed-v7-ml-annotations-6
with an alias.ml-annotations-6
.The text was updated successfully, but these errors were encountered: