[[fix-common-cluster-issues]] == Fix common cluster issues This guide describes how to fix common errors and problems with {es} clusters. <>:: This error indicates a data node is critically low on disk space and has reached the flood-stage disk usage watermark. <>:: {es} uses circuit breakers to prevent nodes from running out of JVM heap memory. If Elasticsearch estimates an operation would exceed a circuit breaker, it stops the operation and returns an error. <>:: The most common causes of high CPU usage and their solutions. <>:: High JVM memory usage can degrade cluster performance and trigger circuit breaker errors. <>:: A red or yellow cluster status indicates one or more shards are missing or unallocated. These unassigned shards increase your risk of data loss and can degrade cluster performance. <>:: When {es} rejects a request, it stops the operation and returns an error with a `429` response code. <>:: A backlogged task queue can prevent tasks from completing and put the cluster into an unhealthy state. <>:: There are multiple reasons why shards might get unassigned, ranging from misconfigured allocation settings to lack of disk space. <>:: A cluster in which nodes leave unexpectedly is unstable and can create several issues. include::common-issues/disk-usage-exceeded.asciidoc[] include::common-issues/circuit-breaker-errors.asciidoc[] include::common-issues/high-cpu-usage.asciidoc[] include::common-issues/high-jvm-memory-pressure.asciidoc[] include::common-issues/red-yellow-cluster-status.asciidoc[] include::common-issues/rejected-requests.asciidoc[] include::common-issues/task-queue-backlog.asciidoc[] include::common-issues/diagnose-unassigned-shards.asciidoc[]