Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
[migration v6.5] Another Kibana instance appears to be migrating the index #25464
Kibana version: 6.5.0
Elasticsearch version: 6.5.0
Server OS version:
Browser OS version:
Original install method (e.g. download page, yum, from source, etc.):
Describe the bug:
Steps to reproduce:
At that point the response of aliases cat request are :
and if i try to restart the Kibana service, i have an empty page in the browser and in the logs i have this message:
I delete .kibana_2 index as mentioned in the logs, using this Curl request:
I restart Kibana and i have this message:
I delete .kibana_1 index as mentioned in the logs, using this Curl request:
I restart Kibana and this time everything works, Kibana is back on the browser, and in the logs i have the logs:
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context:
@CamiloSierraH - thanks for the report. This issue is caused by stopping the process which is in charge of handling the migration. This "locking" is to handle having multiple Kibana instances.
With this issue I see two possible problems:
There is more information available here: https://www.elastic.co/guide/en/kibana/current/upgrade-migrations.html
Same issue - upgraded from 6.4.0 to 6.5.0 using DEB package - appears to be stuck on "Another Kibana instance appears to be migrating the index. Waiting for that migration to complete. If no other Kibana instance is attempting migrations, you can get past this message by deleting index .kibana_2 and restarting Kibana."
Deleting .kibana_2 and restarting causes the same thing to happen, gets stuck on message above.
Kibana UI says "Kibana server is not ready yet" -- cannot access /status either, same message.
@gmeriaux you need to follow this steps to have back your kibana instance -> https://www.elastic.co/guide/en/kibana/current/release-notes-6.5.0.html#known-issues-6.5.0
added a commit
Dec 14, 2018
I noticed that Kibana should be at full stop before deleting the indices. Although Kibana remained slow for a few minutes right before restarting - perhaps to reconstruct the both indices - it came up with all the data intact.
i have the error message: "Another Kibana instance appears to be migrating the index. Waiting for that migration to complete. If no other Kibana instance is attempting migrations, you can get past this message by deleting index .kibana_1 and restarting Kibana."
I had the same problem migrating from
I solved deleting the 3 indexes:
I used the following command from linux bash: