Elasticsearch Loaded Master Nodes

Elasticsearch Loaded Master Nodes

Opster Team

March 2021

In addition to reading this guide, we recommend you run the Elasticsearch Health Check-Up. It will detect issues and improve your Elasticsearch performance by analyzing your shard sizes, threadpools, memory, snapshots, disk watermarks and more.

The Elasticsearch Check-Up is free and requires no installation.

Run the Elasticsearch check-up to receive recommendations like this:

checklist Run Check-Up

The following configuration error was detected on node 123...



This error can have a severe impact on your system. It's important to understand that it was caused by...



In order to resolve this issue and prevent it from occurring again, we recommend that you begin by changing the configuration to...


X-PUT curl -H "Content-Type: application/json" [customized recommendation]


Sometimes you can observe that the CPU and load on one of your master nodes is higher than on others.

This is absolutely normal behavior assuming that the loaded master node is the elected master. Although you need more than one master node (and ideally an odd number), only one of these nodes will be active at any one time. If CPU is very high and the node appears to be overloaded, then this may be cause for concern, since an overloaded master node may cause instability in the cluster.

How to resolve it

How to fix loaded master nodes

  1. Check for split brain

    If you are using an Elasticsearch version earlier than 7, then make sure you are not suffering from the split brain problem described here: Elasticsearch Split Brain – A Thorough Guide, Including How To Avoid It.

  2. Check other processes

    Ensure that there are no other processes running on the master node which could cause it to become unstable. 

  3. Check the master node logs

    Check the loaded master node logs. If the elected master is loaded, the log can reveal the potential causes, such as: high rate of mapping exceptions, too many doc types (for ES versions older than v6), or large metadata – too many fields/indices/shards.

Run the Check-Up to get a customized report like this:

Analyze your cluster