-
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
Kibana exits with a fatal crash if ES cluster status is red #33316
Comments
Pinging @elastic/kibana-platform |
As discussed with @bhavyarm, I can reproduce something similar on my machine where I get |
After some investigation, the error comes from https://github.com/elastic/kibana/blob/master/src/legacy/server/saved_objects/migrations/core/elastic_index.ts#L197, changing the |
Saw the error again on 7.0.0 BC1. But without any mixups. Kibana restarted without any problems at the second try. |
I got a crash when Kibana started up, got to green status initially, then went to red because Elasticsearch queries resulted in
|
May have been fixed in #51324 |
I was able to create a red cluster status by changing this line:
to: const settings = { number_of_shards: 1, auto_expand_replicas: '0-1', 'index.routing.allocation.require._name': 'haskibanaindex', }; The following will start ES in a green state:
Whereas this will result in a red ES cluster when kibana starts up:
I can confirm that a red ES cluster causes Kibana to crash in 7.3.0 and that it no longer crashes in 7.5.0 (fixed in #51324). However, even though Kibana no longer crashes in 7.5, it does not automatically recover when the ES cluster goes from RED -> GREEN but requires a restart of Kibana. This might be due to security and the way I'm reproducing this error. |
I am also facing this issue when Kibana Pod goes into CrashLoopBackOff with the below error. I am using Elastic Stack 7.2.0
|
@rudolf did we decide not to fix this for 7.9? |
Both the reports happen when we check for outdated documents in the In v7.5.0 #51324 we started retrying 503 errors like these indefinitely so if the cluster eventually recovers the migration will succeed. |
Kibana version: 7.0.0 rc1 BC1
Elasticsearch version: 7.0.0 rc1 BC1
Server OS version: darwin_x86_64
Original install method (e.g. download page, yum, from source, etc.): from staging
Describe the bug:
If ES cluster status is red - Kibana is exiting with a fatal error. Multiple restarts of Kibana and ES are not fixing the error.
Please note this bug is an accidental catch.
Steps to reproduce:
ES logs:
Kibana logs:
Cluster status:
.kibana documents are zero:
The text was updated successfully, but these errors were encountered: