The config on my nodes is: Running version 5.3.0 of ES,Logstash, and Kibana 8 CPUs 250gig SSD drives They have 40 Gigs of RAM I allocated 16 gigs to the heap 5 ES nodes Index configured for 5 shards, 1 replica avg shard size for the index is about 20 gigs (a little over 20,000,000 docs) avg CPU ut…

I do not see anything obviously wrong with it, but as you are using VMs I would recommend that you verify that Elasticsearch actually has access to the resources you have specified. memory ballooning or overallocation of CPU can have significant negative impact on performance. Each query or aggrega…

I think my heap is sized right but searches are still super slow

Elastic Stack Elasticsearch

red888 (red der) May 1, 2017, 11:30am 7

VMs, usually just 5 to 10 shards. I'm just using the discover pane in kibana.

But with my current config are there any red flags?

Will increasing the number of shards to utilize more CPU and improve performance?

Topic		Replies	Views
ES used heap % grows slowly until system becomes unresponsive Elasticsearch	21	5522	July 5, 2017
35 shards but maxing out JVM heap Elasticsearch	12	3889	April 5, 2018
Jvm Heap Size & Indexing Perfmance Problem Elasticsearch	1	460	March 11, 2020
Performance issues that make no sense Kibana	10	1244	July 28, 2017
Bulk indexing via ES HTTP Elasticsearch	3	345	July 6, 2017

I think my heap is sized right but searches are still super slow

Related Topics