-
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
Could not find user-provided settings for this version of Kibana (5.0.0-snapshot) #7424
Comments
I think I found a way to consistently reproduce this issue!
|
Don't turn Kibana plugin red if Kibana index is not yet ready
I'm reopening this because I think my current fix is a bit too harsh. It is doing this: after the Elasticsearch goes green the first time, if we ever can't find user settings in the Kibana index after that, we turn the Kibana plugin red. But we never go back and turn the Kibana plugin green if Elasticsearch re-creates the Kibana index and we're able to find the user settings again. After discussing with @LeeDr and @bevacqua, we feel that it is sufficient to log a warning in the server log about missing user settings in the scenario above. The Kibana index being deleted (after initial creation) is not a normal case (i.e. Kibana would never itself do it; the user or tests would have to be mucking with it manually) and, even in that case, the index does get recreated by the Elasticsearch plugin. So for the short period of time the index might not exist, its okay if the user settings are returned as empty and a warning is logged. |
Upon even further discussion 😄 we agreed to go with the stricter option: turn the Kibana plugin red if user settings are not available (the code is doing this already) but also make sure to turn it back to green when the user settings are available again (the code needs to do this). Detailed transcript of discussion: |
Mirror ES status; set own status to red if user settings are not found
Former-commit-id: 273c349
Mirror ES status; set own status to red if user settings are not found Former-commit-id: 9714484
This message seen in the Kibana status page has come up a few times.
I just hit it again.
Refreshing the page several times had no affect.
I restarted Kibana and now it's gone.
@simianhacker hit in on June 7th. I think he restarted and it went away.
I don't see anything related to it in the kibana log.
The text was updated successfully, but these errors were encountered: