Elasticsearch Loaded Client Nodes

Opster Team

Nov 1, 2021 | 1 min read


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.

In addition to reading about loaded client nodes in Elasticsearch and understanding how to handle the issue, 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

Overview

Sometimes you can observe that the CPU and load on some coordinating nodes (client nodes) is higher than others.

This can be caused by applications that are not load balancing correctly across the coordinating nodes, and are making all their HTTP calls to just one or some of the nodes.

Possible effects

A saturated coordinating node could cause an increase in search or indexing response latency, or an increase in write queue/search queue when the cluster is under load (despite there being processing capacity on data nodes). Eventually this could lead to queries timing out.

How to resolve it

You should fix this by putting a load balancer in front of your Elasticsearch nodes, or by including ALL of the nodes in the client application.

es = Elasticsearch(
    ['clientNode1', 'clientNode2','clientNode3'],
    http_auth=('user', 'secret'),
    scheme="https",
    port=443,
)

The above example is how you can load balance across 3 nodes (you should include all the nodes) when using the python client without a load balancer. All of the official Elasticsearch clients use similar arrays in their construction.



Find and fix issues Elasticsearch issues, try AutoOps

Watch product tour

Try For Free
Skip to content