A second/third .kibana index is created after each upgrade

Elastic Stack Kibana
1

51
Screenshot 2019-11-06 at 11.01.51.png899×69 4.47 KB

Hi,

any idea, what I did wrong? After each upgrade for example from 5 - 6 , from 6.8 -> 7.3.2 , 7.3.2 -> 7.4.0 I get another nice .kibana_x index created. Nicely numbered one of another. Some have data, some not. Any idea, why this is happening? I am normally deleting the oldest one, so only one is left which has the alias. Now with 7.4.0 the .kibana_task_manager_x is also doubled.... Any idea, why this is happening?

Thanks a lot

Olaf

2

Hello Olaf,

Preserving the old index but updating the .kibana alias is done by design. Here's some background on this process.

Regards,
Aaron

3

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