Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Sanity check internal index settings #24266

Closed
jbudz opened this issue Oct 19, 2018 · 4 comments
Closed

Sanity check internal index settings #24266

jbudz opened this issue Oct 19, 2018 · 4 comments
Labels
enhancement New value added to drive a business result Feature:Saved Objects Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@jbudz
Copy link
Member

jbudz commented Oct 19, 2018

Occasionally global settings can impact internal index (.kibana,.reporting, etc) settings and cause issues. One example is a long or disabled refresh interval, causing delays with saves.

We can check these values on startup and provide warnings.
@jbudz jbudz added Team:Operations Team label for Operations Team enhancement New value added to drive a business result labels Oct 19, 2018
@rudolf
Copy link
Contributor

rudolf commented Jul 29, 2019 •
edited
Loading

Another example that I've seen a few times is when kibana is kept running while all ES data is deleted and the cluster restarted. Kibana will then write to the .kibana index and start failing in ways that doesn't make it obvious what the underlying issue is.

Because these errors are so cryptic and debugging is so painful, I think it's worth periodically doing this "index health check" and not just on startup.

@rudolf
Copy link
Contributor

rudolf commented Mar 31, 2020

This will be solved by #49764

@rudolf rudolf added Feature:Saved Objects Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc labels Mar 31, 2020
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform (Team:Platform)

@rudolf rudolf removed the Team:Operations Team label for Operations Team label Mar 31, 2020
@jbudz
Copy link
Member Author

jbudz commented Mar 31, 2020

I'm going to close this out as duplicate :). Feel free to reopen if you want

@jbudz jbudz closed this as completed Mar 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New value added to drive a business result Feature:Saved Objects Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rudolf @jbudz @elasticmachine