-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[migration v6.5] recreate .kibana index #25796
Comments
Are these logs from the original upgrade? Or when you tried resetting your index? It looks like Elasticsearch became un-available around the same time it began migrating the index. Can you confirm this? |
This log arrive when I try reset my index. elasticsearch stay available on my two networks configured (eth1.11 et local) I don't know if it can help, here is the mapping applied to .kibana_1:
} |
Pinging @elastic/kibana-platform |
Pinging @elastic/kibana-operations |
experiencing the same problem but forgot to set back: "cluster.routing.allocation.enable": null |
@LordBonkerz Thanks a lot, everything work better after set back "cluster.routing.allocation.enable": null. A error message more explicit could be a good improvement. |
Thanks all, This cause is new to me. Is there something we could be checking for in Kibana to identify this? Is disabling shart allocation a normal practice during an upgrade? |
Disabling shard allocation is advice for elasticsearch upgrade. When you upgrade ELK stack, you need be very careful to finish elasticsearch upgrade before begin kibana upgrade. |
This happened to me too! Would be very nice to have a better error message. |
this error message is still the same, and the only way I was able to get here, was by searching the error AFTER the fact. Could this be a warning when upgrade is initiated? - this is really frustrating to deal with |
Kibana version: 6.5
Elasticsearch version: 6.5
Server OS version: debian 8
Browser version:
Browser OS version:
Original install method (e.g. download page, yum, from source, etc.): apt-get
Describe the bug: Since yesterday, I tried upgrade ELK stack to 6.5 and I am stuck on kibana part. At the beginning, I was thinking this bug this bug was like this but it is strange because I haven't got X-Pack Security.
I tried delete .kibana_1, .kibana_2 without success so I finished by delete .kibana to reset my index.
When I restart kibana I have finally a strange timeout.
In kibana.stdout :
{"type":"log","@timestamp":"2018-11-16T11:20:01Z","tags":["info","migrations"],"pid":18753,"message":"Creating index .kibana_1."} {"type":"log","@timestamp":"2018-11-16T11:20:32Z","tags":["status","plugin:spaces@6.5.0","error"],"pid":18753,"state":"red","message":"Status changed from yellow to red - Request Timeout after 30000ms","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"} {"type":"error","@timestamp":"2018-11-16T11:20:32Z","tags":["fatal","root"],"pid":18753,"level":"fatal","error":{"message":"Request Timeout after 30000ms","name":"Error","stack":"Error: Request Timeout after 30000ms\n at /usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:355:15\n at Timeout.<anonymous> (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:384:7)\n at ontimeout (timers.js:498:11)\n at tryOnTimeout (timers.js:323:5)\n at Timer.listOnTimeout (timers.js:290:5)"},"message":"Request Timeout after 30000ms"}
In elasticSearch.log :
[2018-11-16T12:19:45,897][INFO ][o.e.c.m.MetaDataDeleteIndexService] [skNMpPx] [.kibana/7wEYtjwTT3alUWJM9bwClg] deleting index [2018-11-16T12:20:00,734][INFO ][o.e.c.m.MetaDataIndexTemplateService] [skNMpPx] adding template [.management-beats] for index patterns [.management-beats] [2018-11-16T12:20:01,998][INFO ][o.e.c.m.MetaDataCreateIndexService] [skNMpPx] [.kibana_1] creating index, cause [api], templates [], shards [1]/[1], mappings [doc] [2018-11-16T12:20:01,999][INFO ][o.e.c.r.a.AllocationService] [skNMpPx] updating number_of_replicas to [0] for indices [.kibana_1] [2018-11-16T12:20:02,001][INFO ][o.e.c.r.a.AllocationService] [skNMpPx] Cluster health status changed from [YELLOW] to [RED] (reason: [index [.kibana_1] created]).
I didn't success to downgrade also elastic in 6.4.3.
Steps to reproduce:
Expected behavior:
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context:
The text was updated successfully, but these errors were encountered: