Elasticsearch Loaded Master Nodes

Elasticsearch Loaded Master Nodes

Opster Team

July 2020, Version: 1.7-7.9

In addition to reading this guide, run the free Elasticsearch Health Check-Up. Get actionable recommendations that can improve performance and prevent incidents (does not require any installation). Among the dozens of checks included are: shards sizes, search errors, thread pools, management queue size, circuit breakers and many more. Join over 700 users who use this free tool.

What Does it Mean

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

Improve Elasticsearch Performance

Run The Analysis