Elasticsearch Loaded Client Nodes/Coordinating Nodes



Elasticsearch Loaded Client Nodes/Coordinating 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 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 Fix 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.





Improve Elasticsearch Performance

Run The Analysis