mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-24 23:27:25 -04:00
17 lines
876 B
Text
17 lines
876 B
Text
[[diagnose-unassigned-shards]]
|
|
== Diagnose unassigned shards
|
|
|
|
There are multiple reasons why shards might get unassigned, ranging from misconfigured
|
|
allocation settings to lack of disk space.
|
|
|
|
In order to diagnose the unassigned shards in your deployment use the following steps:
|
|
|
|
include::{es-ref-dir}/tab-widgets/troubleshooting/data/diagnose-unassigned-shards-widget.asciidoc[]
|
|
|
|
See https://www.youtube.com/watch?v=v2mbeSd1vTQ[this video]
|
|
for a walkthrough of monitoring allocation health.
|
|
|
|
****
|
|
If you're using Elastic Cloud Hosted, then you can use AutoOps to monitor your cluster. AutoOps significantly simplifies cluster management with performance recommendations, resource utilization visibility, real-time issue detection and resolution paths. For more information, refer to https://www.elastic.co/guide/en/cloud/current/ec-autoops.html[Monitor with AutoOps].
|
|
****
|
|
|