I have around 2GB of events getting accumulated every day. I use curator to get rid of data every 5 days. Now, the problem is it takes long time to execute search in kibana. I am using docker to run ELK . When I do docker stats , I can see that only 3 GB of memory is getting used when I have 64GB a…

You really only need 1 primary shard for 2GB of data, anymore is just wasteful and likely to cause slower response times, as the heap will be taken up managing mostly empty shards.

Discuss the Elastic Stack

Terribly slow kibana query

Elastic Stack Kibana

warkolm (Mark Walkom) July 5, 2019, 8:18am 8

It might be easier to keep things to a single thread, as you also have this one going too - Increase shards and replicas in new Index

Topic		Replies	Views
I think my heap is sized right but searches are still super slow Elasticsearch	9	1551	May 29, 2017
Kibana/ES too slow - Discover view Kibana docker	4	785	September 22, 2021
Kibana's "Heap Total" Kibana	3	1650	May 31, 2017
Kibana response time is slow Elasticsearch	3	2664	July 5, 2017
How to change kibana heap size Kibana	3	472	September 11, 2019

Elasticsearch is a trademark of Elasticsearch BV, registered in the U.S. and in other countries
Trademarks
Terms
Privacy
Brand
Code of Conduct

Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant logo are trademarks of the Apache Software Foundation in the United States and/or other countries.

Terribly slow kibana query

Related topics