So the 7.0 Upgrade Assistant for Kibana 6.6.0 is complaining that the searchguard index is too old, as it was created in ES 5.4.2.
What’s the best course of action for getting this reindexed as 6.6.0, considering I can’t easily access the searchguard index?
I do have all my roles, etc as YAML, so I could potentially just remove the searchguard index and re-create it with sgadmin.sh, but I’d prefer to have no downtime.
We will post/document some informations on this with the first beta release of ES 7.0.0
Stay tuned ...
···
Am 14.02.2019 um 03:01 schrieb CK <posthamster@gmail.com>:
HI there,
So the 7.0 Upgrade Assistant for Kibana 6.6.0 is complaining that the searchguard index is too old, as it was created in ES 5.4.2.
What's the best course of action for getting this reindexed as 6.6.0, considering I can't easily access the searchguard index?
I do have all my roles, etc as YAML, so I could potentially just remove the searchguard index and re-create it with sgadmin.sh, but I'd prefer to have no downtime.
I ended up re-creating my searchguard index.
Surprisingly, search-guard continued working during the time there was no index. Is this normal behaviour? For how long can one delete the index?
sgadmin will delete and re-cretae the searchguard index during the upgrade procedure.
Search Guard will continue to work when the sg index is deleted as long as not all datanodes are going down at the same time (because the config is cached in memory)