Skip to content

[5.x] settings: do not query ES for settings in non-green status#9310

Merged
epixa merged 1 commit into5.xfrom
jasper/backport/9308/5.x
Dec 1, 2016
Merged

[5.x] settings: do not query ES for settings in non-green status#9310
epixa merged 1 commit into5.xfrom
jasper/backport/9308/5.x

Conversation

@elastic-jasper
Copy link
Contributor

settings: do not query ES for settings in non-green status

Backports PR #9308

Commit 1:
settings: do not query ES for settings in non-green status

If the ui settings status is not green, that means there is at least one
dependency (so elasticsearch at the moment) that is not met in order for
it to function correctly, so we shouldn't attempt to determine user
settings at all.

This ensures that when something like the version check fails in the
elasticsearch plugin, Kibana correctly behaves by not attempting
requests to elasticsearch, which prevents 500 errors and allows users to
see the error status on the status page.

We also now periodically check for compatible elasticsearch versions so
that Kibana can automatically recover if the elasticsearch node is
upgraded to the appropriate version.

Backports PR #9308

**Commit 1:**
settings: do not query ES for settings in non-green status

If the ui settings status is not green, that means there is at least one
dependency (so elasticsearch at the moment) that is not met in order for
it to function correctly, so we shouldn't attempt to determine user
settings at all.

This ensures that when something like the version check fails in the
elasticsearch plugin, Kibana correctly behaves by not attempting
requests to elasticsearch, which prevents 500 errors and allows users to
see the error status on the status page.

We also now periodically check for compatible elasticsearch versions so
that Kibana can automatically recover if the elasticsearch node is
upgraded to the appropriate version.

* Original sha: 43742b2
* Authored by Court Ewing <court@epixa.com> on 2016-12-01T17:02:19Z
@elastic-jasper elastic-jasper added the backport This PR is a backport of another PR label Dec 1, 2016
@epixa epixa merged commit 2735a32 into 5.x Dec 1, 2016
@epixa epixa deleted the jasper/backport/9308/5.x branch December 1, 2016 18:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport This PR is a backport of another PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants