Not able to start Kibana due “another Kibana instance appears to be migrating the index”

Solved1.07K viewsElasticsearch Kibana
0
0 Comments

Hello,
I have trouble starting Kibana on one of our agents of a test cluster.
Did anyone already encountered this and how can we fix this?

Debeuf Klaas [SLC] [DevOps Advocate] Selected answer as best 3rd September 2021

2 Answers

3
359 0 Comments

Hi Klaas,

The issue is not DataMiner related, but is related to the process stopping while still being busy with the migration. Elastic locks this index to protect itself, but this causes Kibana to not be accessible anymore.

You can fix this by deleting the locked .kibana_1 index. As you cannot do this in Kibana, you can send the delete query via git bash (right click on a random folder - Git Bash Here) and send the following query:

curl -XDELETE http://[YOURIP]:9200/.kibana_1

Debeuf Klaas [SLC] [DevOps Advocate] Selected answer as best 3rd September 2021
You are viewing 1 out of 2 answers, click here to view all answers.