search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.63k stars 8.22k forks source link

Upgrade Assistant: Elasticsearch deprecations shown as manual but are handled by reindexing should it be shown? #116210

Open liza-mae opened 3 years ago

liza-mae commented 3 years ago

Kibana version: 7.16.0

Elasticsearch version: 7.16.0

Server OS version: Cloud

Browser version: Chrome

Browser OS version: Latest

Original install method (e.g. download page, yum, from source, etc.): Staging

Description of the problem including expected versus actual behavior: In UA, upgrade path 6.8.20 -> 7.16.0, I noticed some elasticsearch deprecations shown as manual but are handled by reindexing. They have to do with index.routing.allocation.include._tier_preference and reindexing the Index created before 7.0 clears it. Should they be shown at all?

Screenshot from 2021-10-25 13-21-08

elasticmachine commented 3 years ago

Pinging @elastic/kibana-stack-management (Team:Stack Management)

cjcenizal commented 3 years ago

Thanks for finding this @liza-mae! I agree that this is a confusing UX. However, as you point out there's a "workaround" in that automatically reindexing one item will address the corresponding "manual" item.

Solving this UX confusion will require us to deduplicate messages for indices which can be automatically reindexed, but only for those messages that will actually be addressed by the reindex, and adding test coverage. I think this scope of work falls beyond what we're capable of post-FF. This, coupled with the above workaround, leads me to decide we should defer this to an enhancement in a future release.