here is error.
java.lang.IllegalStateException: cannot upgrade node because incompatible indices created with version [6.5.4] exist, while the minimum compatible index version is [7.0.0]. Upgrade your older indices by reindexing them in version [7.17.0] first.
now I can't find which one is old index. I found some thread but still can't figure out how to fix it.
https://github.com/elastic/elasticsearch/pull/91243
this git issue is for that but how to upgrade or fix something before hand.
https://discuss.elastic.co/t/upgraded-first-node-from-7-17-5-to-8-4-wont-start-claiming-there-is-a-6-4-5-index-but-i-cant-find-it/317811/10
Referring to this discussion thread.
@DavidTurner created this. Can someone help me to find out which node it is.
update:
and found one index .kibana_1 created_string: 6.5.4
can I just delete that index and try again?
stephenb
December 23, 2022, 8:14pm
3
Are you running the upgrade assistant?
And yes 6.x indices can not migrate to 8.x AFAIK.
I would be surprised if that index is still in use... If you choose to delete it make sure you have a backup.
But to be clear not my area of deep expertise... Just thinking out loud
2 Likes
upgrade assistant didn't say anything about index.
they way I do upgrade is shutdown everything,
I did upgrade one smaller cluster and had no such issue.
After deleting that index now that part is green
one more question. I have multiple datapath is define. can I upgrade with MDP
https://github.com/elastic/elasticsearch/issues/71205#issuecomment-1089281310
it says critical but it should be warning as per thishttps://github.com/elastic/elasticsearch/issues/85695
stephenb
December 23, 2022, 9:12pm
6
Perhaps you should upgrade to 7.17.6 (I know painful)
Looks like that was moved to warning in 7.17.4 per this.. if it made I see backport failed but you could try..
elastic:master ← rjernst:mdp/deprecation2
opened 01:19PM - 18 Apr 22 UTC
The deprecations for index and shared data paths were defined at
critical level… , but these are not removed in 8.0. This commit relaxes
these deprecation messages so they are just warnings.
relates #85695
And yes multiple data paths are still supported but deprecated...
And the deprecation notice and migration planning
1 Like
DavidTurner
December 24, 2022, 10:45am
7
I think this is a bug. I can see at least one way for this to happen: if the index is hidden. I opened a bug report:
opened 10:44AM - 24 Dec 22 UTC
>bug
:Core/Infra/Core
Team:Core/Infra
Feature:Upgrade Assistant
For instance, we do not report that an index created in 6.8 needs to be removed … before upgrading if the index is hidden:
```
GET /
# 200 OK
# {
# "cluster_name": "elasticsearch",
# "tagline": "You Know, for Search",
# "name": "node-0",
# "version": {
# "build_snapshot": false,
# "build_hash": "8d61b4f7ddf931f219e3745f295ed2bbc50c8e84",
# "minimum_index_compatibility_version": "6.0.0-beta1",
# "build_flavor": "default",
# "minimum_wire_compatibility_version": "6.8.0",
# "build_date": "2022-06-23T21:57:28.736740635Z",
# "number": "7.17.5",
# "build_type": "tar",
# "lucene_version": "8.11.1"
# },
# "cluster_uuid": "5njmzfeoTPOCgQAgAGjbiQ"
# }
GET /oldindex/_settings?flat_settings
# 200 OK
# {
# "oldindex": {
# "settings": {
# "index.creation_date": "1671876986121",
# "index.hidden": "true",
# "index.version.created": "6082099",
# "index.provided_name": "oldindex",
# "index.uuid": "Ff4U1IxmTLGIICAyiFwbww",
# "index.number_of_shards": "1",
# "index.number_of_replicas": "0"
# }
# }
# }
GET /_migration/deprecations
# 200 OK
# {
# "index_settings": {},
# "ccr_auto_followed_system_indices": [],
# "node_settings": [],
# "cluster_settings": [],
# "ml_settings": []
# }
```
Was this index hidden? If not, can you share its settings so we can see why else it might have been skipped?
2 Likes
yes it was hidden index .kibana_1 and .reporting
1 Like
just a update.
1 Like
system
January 21, 2023, 11:03pm
10
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
