Elasticsearch cluster performance tuning

Following an error I got in Kibana and the following posts

How can I optimise and tune the elastic cluster?

  • Elasticsearch/Kibana version are 7.6.2
  • I have 5 nodes in the cluster, all run on a CentOS 7 VMs
  • 28G per node for JVM
  • File swap is disabled on all nodes
  • Using shards calculation according to this article.


I have not seen the article you linked to before. How many indices and shards do you have? What is the average size?

Currently I have
~ 700 indices
~ 2240 shards
~ 53GB Average size (primary+replica)


What issues are you having? What is it you want to tune for?

Currently Kibana is hitting a timeout exception/error.
In the first link I gave, the user named @flash1293, advises to

Maybe it is possible to tune your server a bit without adding hardware. For guidance around this you can post in the ES forum and I'm sure you will find help.

So I am trying to understand if there is any further optimisation I can do on the cluster?!

The first thing to do is identify what is causing the timeouts.

If you look in the Elasticsearch logs, do you see indications of long and/or frequent GC? You have a lot of data on each node so it is possible that you are suffering from heap pressure.

What does CPU usage look like while you have queries timing out? Is any node saturated?

The last thing that commonly causes timeouts is issues around storage performance. Are you monitoring disk utilisation and iowait? What does disk usage look like during query timeouts?

Hi @Christian_Dahlqvist
You have good questions. Unfortunately, I cannot answer them right now as I am not monitoring all those metrics. It will require some more time/effort.

In the short run, I am planning to monitor query times.
In the longer run, I would sure want to monitor more metrics and understand what is affecting the performance.


Hi @Christian_Dahlqvist
Any recommendations regarding Monitor queries running time?
What is the best way to do it?

Do you have Elasticsearch monitoring enabled?

What do you mean?
Not sure how to answer.


Have a look at the docs around monitoring.

currently, monitoring with filebeat and metricbeat.
trying to configure packetbeat for query runtime.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.