-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[8.0 Upgrade Assistant] Reindex failed when the index was ever frozen #40564
Comments
I opened an issue for this on the ES side to be able to determine whether a setting is private: elastic/elasticsearch#44440 |
@dakrone do you know if there is manual way to get the customer past this point? to be able to upgrade his indices? |
@joshFive they can manually re-index, copying only the non-private settings (in this case, the |
Pinging @elastic/es-ui |
This should be addressed via #91193. The Upgrade Assistant was updated to handle these private ES settings. |
I wanted to add that while the underlying code has been fixed, starting in |
Kibana version: 7.2.0
Elasticsearch version: 7.2.0
Describe the bug:
When Elasticsearch and Kibana at 6.x, some indices were ever frozen/unfrozen, so the index settings is added following private settings:
After upgrading Elasticsearch and Kibana from 6.x to 7.2, running 8.0 Upgrade Assistant, it prompts to convert the index created before 7.0 should be reindexed. However, the step
creating new index
failed with following error:Looks like, when creating index, the index private settings are also used, which is not allowed.
Steps to reproduce:
After that, even unfreeze, the settings are still there.
2. Upgrade ES/Kibana from 6.x to 7.2.0.
3. Run Kibana >
8.0 Upgrade Assistant
>Indices
> clickReindex
forIndex created before 7.0
, then it would fail with errors.Expected behavior:
Private settings of index should be excluded when creating new index with format 7.0.
The text was updated successfully, but these errors were encountered: