I upgrade kibana from 7.11.1 to 7.12.0 the process has been finished the index has green status and I have access to kibana but I check .kibana_task_manager_7.12.0_001 index and looks like it still reindex
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .kibana_task_manager_7.12.0_001 a6xg7wAJTWCoFUitL7ZAas 1 1 10 41463 9.5mb 3.8mb
green open .kibana_task_manager_1 Qi6DrGASQMeYGVm1fT7GGw 1 1 9 48267 4.8mb 4.7mb
how can I know that .kibana_task_manager_7.12.0_001 has been migrated and it safe remove .kibana_task_manager_1
I confirm that kibana started up successfully, there isn't any error in kibana logs, I only saw .kibana_task_manager_7.12.0_001 index is keeping increase, my first assumption is that .kibana_task_manager_7.12.0_001 was being reindexed from .kibana_task_manager_1 and keeping reindex it after kibana came up, but now I see that .kibana_task_manager_7.12.0_001 is keeping increase even more than .kibana_task_manager_1. My assumption is that .kibana_task_manager_7.12.0_001 index is increasing as normal behaviour and it isn't related with reindex from .kibana_task_manager_1
Hi, I wouldn't worry about the system indices like .kibana_task_manager* because they are internal implementation details that Kibana needs to manage itself to work properly. Fortunately, it looks like this is a very small index that isn't costing much storage space.
I'll check with the Alerting team here at Elastic to see if there was some kind of bug that made cleanup of the old index fail.
Hi, thank you for reply me, I really appreciate your advise,
fyi
Here is the actual size for .kibana_task_manager_7.12.0_001
health status index uuid pri rep docs.count docs.deleted store.size pri.store.size
green open .kibana_task_manager_7.12.0_001 a6xg7wAJTWCoFUitL7ZAas 1 1 10 130569 22.6mb 11.3mb
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.