Operations

The cluster concurrent rebalance setting determines the maximum number of shards the cluster can move to rebalance the distribution of...

When the “disk flood stage” threshold is passed on an Elasticsearch cluster, it will start to block core actions. To resolve this issue...

Heavy merges use CPU, memory and disk resources, which can slow down the cluster’s response speed. In order to fix...

Cluster pending tasks are updates to the cluster state which may have been initiated directly by a user or by the cluster itself. When...

High CPU is often a symptom of other underlying issues. It should be fixed because a distressed node will slow query response time and...

The high disk watermark is one of the various thresholds on your ES cluster. It's important to understand what it means and how to handle...

A high number of tasks in management queue can cause Elasticsearch cluster instability which could result in data loss. To resolve...

Circuit breaker exceptions are thrown to alert us that something needs to be fixed in Elasticsearch in order to reduce memory usage. To fix...

Once an indexing queue exceeds the maximum size, the Elasticsearch node will start rejecting index requests. To resolve this, check the...

A saturated coordinating node could cause an increase in search or indexing response latency. This can be fixed by putting a load balancer...

Sometimes you can observe that the CPU and load on some of your data nodes is higher than on others. This can occasionally be caused by...

An overloaded master node may cause instability in the cluster. There are 3 ways to fix loaded master nodes: (1) Checking for...

Low disk watermark is one of the various thresholds on your Elasticsearch cluster. Here are possible actions you can take to resolve...

An Elasticsearch cluster requires a master node to be identified in the cluster in order for it to start properly. If the cluster lacks a...

If 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...

It's important to realize that node disconnection is often a symptom of underlying problems which must be found and solved - learn how to...

A large number of shards on an Elasticsearch cluster requires extra resources. Learn key ways to avoid and correct oversharding...

There are a number of reasons why a search request can be rejected by the Elasticsearch cluster. To resolve the issue, you need to...

If the Elasticsearch cluster starts to reject search requests, there could be a number of causes. Generally it indicates that...

Elasticsearch usually balances index shards evenly across all of the active data nodes in the cluster. If this isn't happening it's because..

It is a best practice that Elasticsearch shard size should not go above 50GB for a single shard. If you go above this limit...

If the indexing queue is high or produces time outs, it indicates that one or more Elasticsearch nodes cannot keep up with the rate of...

Elasticsearch red status indicates not only that the primary shard has been lost, but also that a replica has not been promoted...

Yellow status indicates that one or more of the replica shards on the Elasticsearch cluster are not allocated to a node. This could occur...