# Upgrade from 7.17.1 to 8.5.3 failed

**URL:** <https://discuss.elastic.co/t/upgrade-from-7-17-1-to-8-5-3-failed/321946>\
**Category:** Elasticsearch\
**Created:** [December 23, 2022, 7:55pm UTC](https://discuss.elastic.co/t/upgrade-from-7-17-1-to-8-5-3-failed/321946 "2022-12-23T19:55:48Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [December 23, 2022, 7:55pm UTC](https://discuss.elastic.co/t/upgrade-from-7-17-1-to-8-5-3-failed/321946/1 "2022-12-23T19:55:48Z")

</div>

here is error.

```auto

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](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](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.

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [December 23, 2022, 7:59pm UTC](https://discuss.elastic.co/t/upgrade-from-7-17-1-to-8-5-3-failed/321946/2 "2022-12-23T19:59:25Z")

</div>

update:  
ran following  
GET /.\*/\_settings?human

and found one index .kibana\_1 created\_string: 6.5.4

can I just delete that index and try again?  
Man it is big cluster. need to do all this over again...grhhh. 🙄

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [December 23, 2022, 8:14pm UTC](https://discuss.elastic.co/t/upgrade-from-7-17-1-to-8-5-3-failed/321946/3 "2022-12-23T20:14:54Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [December 23, 2022, 8:45pm UTC](https://discuss.elastic.co/t/upgrade-from-7-17-1-to-8-5-3-failed/321946/4 "2022-12-23T20:45:25Z")

</div>

upgrade assistant didn't say anything about index.

they way I do upgrade is shutdown everything,  
upgrade packages, change config if needed ( as i have tested in test cluster) then start up everything

I did upgrade one smaller cluster and had no such issue.

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [December 23, 2022, 8:56pm UTC](https://discuss.elastic.co/t/upgrade-from-7-17-1-to-8-5-3-failed/321946/5 "2022-12-23T20:56:49Z")

</div>

After deleting that index now that part is green

one more question. I have multiple datapath is define. can I upgrade with MDP

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/0/c/0ce04657068d177a229d86f14ba2fda6bc506983.png)

[https://github.com/elastic/elasticsearch/issues/71205#issuecomment-1089281310](https://github.com/elastic/elasticsearch/issues/71205#issuecomment-1089281310)

it says critical but it should be warning as per this  
[https://github.com/elastic/elasticsearch/issues/85695](https://github.com/elastic/elasticsearch/issues/85695)

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [December 23, 2022, 9:12pm UTC](https://discuss.elastic.co/t/upgrade-from-7-17-1-to-8-5-3-failed/321946/6 "2022-12-23T21:12:00Z")

</div>

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..

> <https://github.com/elastic/elasticsearch/pull/85952>
>
> 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...

> **[Important Elasticsearch configuration | Elasticsearch Guide \[8.5\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/important-settings.html#_multiple_data_paths)**

And the deprecation notice and migration planning

> **[Important Elasticsearch configuration | Elasticsearch Guide \[8.5\] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/important-settings.html#mdp-migrate)**

---

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [December 24, 2022, 10:45am UTC](https://discuss.elastic.co/t/upgrade-from-7-17-1-to-8-5-3-failed/321946/7 "2022-12-24T10:45:26Z")

</div>

> [@elasticforme](#):
>
> upgrade assistant didn't say anything about index.

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:

> <https://github.com/elastic/elasticsearch/issues/92560>
>
> 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?

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [December 24, 2022, 9:23pm UTC](https://discuss.elastic.co/t/upgrade-from-7-17-1-to-8-5-3-failed/321946/8 "2022-12-24T21:23:03Z")

</div>

yes it was hidden index .kibana\_1 and .reporting

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [December 24, 2022, 11:03pm UTC](https://discuss.elastic.co/t/upgrade-from-7-17-1-to-8-5-3-failed/321946/9 "2022-12-24T23:03:01Z")

</div>

just a update.  
upgrade is completed.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [January 21, 2023, 11:03pm UTC](https://discuss.elastic.co/t/upgrade-from-7-17-1-to-8-5-3-failed/321946/10 "2023-01-21T23:03:09Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.