Flood Stage Disk WatermarkWhen the “disk flood stage” threshold is exceeded on an Elasticsearch cluster, it will start to block core actions. To resolve this issue...
Heavy Merges Were DetectedHeavy merges use CPU, memory and disk resources, which can slow down the cluster’s response speed. In order to fix...
High Cluster Pending TasksElasticsearch cluster pending tasks are updates to the cluster state that were initiated by a user or the cluster. To resolve, list the...
High CPUHigh CPU is often a symptom of other underlying issues. It should be fixed because a distressed node will slow query response time and...
High Disk WatermarkHigh disk watermark is one of the various thresholds on your Elasticsearch cluster. Passing this threshold is a warning and you should not...
High Management QueueA high number of tasks in management queue can cause Elasticsearch cluster instability which could result in data loss. To resolve...
Index Queue Size Is HighOnce an indexing queue exceeds the maximum size, the Elasticsearch node will start rejecting index requests. To resolve this, check the...
Loaded Client NodesA saturated coordinating node could cause an increase in search or indexing response latency. This can be fixed by putting a load balancer...
Loaded Master NodesAn overloaded master node may cause instability in the cluster. There are 3 ways to fix loaded master nodes: (1) Checking for...
Low Disk WatermarkLow disk watermark is one of the various thresholds on your Elasticsearch cluster. Here are possible actions you can take to resolve...
Master Node Not DiscoveredAn Elasticsearch cluster requires a master node to be identified in the cluster. Reasons why a master node is not discovered yet include...
Max Shards Per Node ExceededIf the max of shards per node is exceeded in Elasticsearch, shards can't be allocated. It is crucial to check if the limit is set at a...
Node DisconnectedAn Elasticsearch node can disconnect from a cluster for several reasons, including: excessive garbage collection from JVM, configuration...
Red StatusElasticsearch red status indicates not only that the primary shard has been lost, but also that a replica has not been promoted...
Search is Slow in nodesNamesThere are a number of possible causes for slow searches on particular nodes. To correct the issue and improve search performance, you...
Search Rejected QueueAn Elasticsearch cluster can start to reject search requests for several reasons. To resolve this, check the state of the thread pool and..
Slow Indexing in NodesIf the indexing queue is high/causes timeouts, it hints that Elasticsearch nodes can't keep up with the indexing rate. To fix slow indexing...
Yellow StatusYellow status indicates that one or more of the replica shards on the Elasticsearch cluster are not allocated to a node. This could occur...