-
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
Why did the kibana index became red usually? #7615
Comments
A red status can mean a lot of things, but it doesn't generally mean that there's a bug. More often than not, the ES plugin triggers a red status when the cluster itself is overloaded or there is a connectivity issue between Kibana and Elasticsearch. For help troubleshooting things like this, please use our forums or irc channel. We reserve github for confirmed bug and feature requests. |
Please see the issue by the link, thks: https://discuss.elastic.co/t/why-did-the-kibana-index-ususally-became-delete-status/55021 |
`v93.5.2` ⏩ `v93.6.0` --- ## [`v93.6.0`](https://github.com/elastic/eui/releases/v93.6.0) - Updated `EuiBreadcrumb` styles to improve visual distinction of clickable breadcrumbs ([#7615](elastic/eui#7615)) **Deprecations** - Deprecated `color` prop on `EuiBreadcrumb` ([#7615](elastic/eui#7615)) **Bug fixes** - Fixed `EuiComboBox` to correctly select full matches within groups via the `Enter` key ([#7658](elastic/eui#7658)) **Accessibility** - Updated `EuiHeaderBreadcrumb` styles to ensure min. required color contrast ([#7643](elastic/eui#7643)) - `EuiSuperSelect` now correctly reads out parent `EuiFormRow` labels to screen readers ([#7650](elastic/eui#7650)) - `EuiSuperSelect` now more closely mimics native `<select>` behavior in its keyboard behavior and navigation ([#7650](elastic/eui#7650)) - `EuiSuperSelect` no longer strands keyboard focus on close ([#7650](elastic/eui#7650)) - `EuiSuperSelect` now correctly allows keyboard navigating past disabled options in the middle of the options list ([#7650](elastic/eui#7650))
Kibana version: 4.1.1
OS version: suse 11
Original install method (e.g. download page, yum, from source, etc.): download
Description of the problem including expected versus actual behavior:
Our business data scale is very large, We use kibana to show the es data.
The kibana index only has 12 document,
But the kibana index usually became red, then kibana page did not work.
Why did the kibana index became red?
The text was updated successfully, but these errors were encountered: