You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When migrating from ElasticSearch to OpenSearch (via the snapshot restore path), indexes can/will be restored with deprecated index settings, e.g. archived.index.lifecycle.name. However, when applying an index policy and switching its state, the ISM fails with the following info: "unknown setting [archived.index.lifecycle.name] please check that any required plugins are installed, or check the breaking changes documentation for removed settings"
Describe the solution you'd like
It would be wonderful, to either let the user delete deprecated "archived" settings or fix the problem for the ISM (the ISM state change should work independently from existing deprecated "archived" settings.
Describe alternatives you've considered
Currently, only a complete reindex will fix these ISM failures. However, reindexing is time and CPU intensive.
Additional context
OpenSearch 1.2.3
Migration from ElasticSearch 7.10.2
archived.index.lifecycle.name isn't an ISM setting, it's an ILM setting from Elastic's x-pack feature (Index Lifecycle Management).
This error: "unknown setting [archived.index.lifecycle.name] please check that any required plugins are installed, or check the breaking changes documentation for removed settings" isn't related much to ISM.. it's the core not knowing what to do with the archived setting that was imported from the snapshot (in this case the x-pack ILM setting, but could be any setting that's in Elasticsearch and not in OpenSearch).
@anasalkouz This isn't really an ISM issue... this is a core issue relating to imported settings that OpenSearch does not support and them being archived and causing the cluster to stop specific API requests (I think it'll block all setting API calls, I forget exactly though). I'd probably move it back to core repo.
The text was updated successfully, but these errors were encountered:
@faabsen commented on Mon Apr 04 2022
Is your feature request related to a problem? Please describe.
When migrating from ElasticSearch to OpenSearch (via the
snapshot restore
path), indexes can/will be restored with deprecated index settings, e.g.archived.index.lifecycle.name
. However, when applying an index policy and switching its state, the ISM fails with the following info: "unknown setting [archived.index.lifecycle.name] please check that any required plugins are installed, or check the breaking changes documentation for removed settings"Describe the solution you'd like
It would be wonderful, to either let the user delete deprecated "archived" settings or fix the problem for the ISM (the ISM state change should work independently from existing deprecated "archived" settings.
Describe alternatives you've considered
Currently, only a complete reindex will fix these ISM failures. However, reindexing is time and CPU intensive.
Additional context
OpenSearch 1.2.3
Migration from ElasticSearch 7.10.2
@dbbaughe commented on Tue Apr 05 2022
archived.index.lifecycle.name
isn't an ISM setting, it's an ILM setting from Elastic's x-pack feature (Index Lifecycle Management).This error:
"unknown setting [archived.index.lifecycle.name] please check that any required plugins are installed, or check the breaking changes documentation for removed settings"
isn't related much to ISM.. it's the core not knowing what to do with the archived setting that was imported from the snapshot (in this case the x-pack ILM setting, but could be any setting that's in Elasticsearch and not in OpenSearch).@anasalkouz This isn't really an ISM issue... this is a core issue relating to imported settings that OpenSearch does not support and them being archived and causing the cluster to stop specific API requests (I think it'll block all setting API calls, I forget exactly though). I'd probably move it back to core repo.
The text was updated successfully, but these errors were encountered: