Operations

Cluster Concurrent Rebalance High / Low

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

Elasticsearch Circuit Breaker Exceptions: How to Handle Circuit Breakers

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

Elasticsearch Hotspots - Load Balancing, Data Allocation and How to Avoid Hotspots

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

Elasticsearch Memory and Disk Usage Management

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

Flood Stage Disk Watermark

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 Were Detected

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

High Cluster Pending Tasks

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

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

High disk watermark is one of the various thresholds on your Elasticsearch cluster. Passing this threshold is a warning and you should not...

High Management Queue

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

Index Queue Size Is High

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

Loaded Client Nodes

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

Loaded Master Nodes

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

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

Master Node Not Discovered

An 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 Exceeded

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

Node Disconnected

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

Red Status

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

Rejected Search Requests in Elasticsearch - Causes and Solutions

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

Search is Slow in nodesNames

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

Search Rejected Queue

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

Slow Indexing in Nodes

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

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