Operations

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

When you try to retrieve a document by ID, Elasticsearch will count the number of times that it searches for an ID which doesn't exist...

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

When Elasticsearch detects that the merge process cannot keep up with the rate of indexing, then it will start to throttle indexing...

"Hotspots" refers to a situation in which a cluster with multiple nodes is not balanced - some nodes are handling more load than others...

One way to evaluate whether your resources are cost efficient it check the ratio of disk usage to the memory allocated...

When upgrading to a new Elasticsearch version, you can use the feature migration APIs to avoid deprecation issues. These APIs simplify...

When the “disk flood stage” threshold is exceeded 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...

Elasticsearch cluster pending tasks are updates to the cluster state that were initiated by a user or the cluster. To resolve, list the...

High 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 watermark is one of the various thresholds on your Elasticsearch cluster. Passing this threshold is a warning and you should not...

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

There are 2 methods to increase the primary shard count in Elasticsearch: _reindex API & the _split API. Before using either method, you…

The 2 approaches for upgrading Elasticsearch versions are full cluster restarts & rolling restarts. Before starting an upgrade, you need...

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

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. Reasons why a master node is not discovered yet include...

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

An Elasticsearch node can disconnect from a cluster for several reasons, including: excessive garbage collection from JVM, configuration...

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

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

There are a number of possible causes for slow searches on particular nodes. To correct the issue and improve search performance, you...

An Elasticsearch cluster can start to reject search requests for several reasons. To resolve this, check the state of the thread pool and..

If 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 status indicates that one or more of the replica shards on the Elasticsearch cluster are not allocated to a node. This could occur...