# Elasticsearch 5.3.2 Merge Spikes and Searchability Delay **URL:** \ **Category:** Elasticsearch\ **Created:** [November 16, 2017, 10:18pm UTC](https://discuss.elastic.co/t/elasticsearch-5-3-2-merge-spikes-and-searchability-delay/108031 "2017-11-16T22:18:24Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![sila5](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sila5/32/22700_2.png) [@sila5](https://discuss.elastic.co/u/sila5)\ **Post date:** [November 16, 2017, 10:18pm UTC](https://discuss.elastic.co/t/elasticsearch-5-3-2-merge-spikes-and-searchability-delay/108031/1 "2017-11-16T22:18:24Z")
I need some help in diagnosing the performance of my elasticsearch cluster. I'm seeing large spikes in merge times and size at the same times each day during busy hours. As a result documents are taking hours sometimes before they become searchable. [resources] I have a 3 node cluster running on m4.large EC2 instances (2 cpu, 8GB mem) each has a 500GB EBS ssd volume attached In front are 2 m4.large instances running logstash that are just doing a simple grok filter I'm using filebeat to send app logs to the logstash instances. There are about 20 instances running filebeat Over a period of 10 hours there are roughly 120 million log lines generated which equals around 150GB of size I'm using the curator plugin to delete indices older than 5 days and force merge indices older than 1 day. Both only run during off hours I'm not seeing any messages in the log files for elasticsearch, logstash or filebeat that indicate a problem. [settings] The elasticsearch cluster settings are default 4GB assigned to JVM on each ec2 instance The index is an edited version of the default logstash template. rotated daily norms and \_all are disabled refresh interval is 30s 6 shards 0 replicas 27 fields total [Versions] elasticsearch 5.3.2 logstash 5.3.2 filebeat 5.6.4 elasticsearch metrics ![ELK_metrics1](https://us1.discourse-cdn.com/elastic/original/3X/e/3/e36cdea444479c2bcbe82a9601b6fbcfbf6b4c40.PNG) ![ELK_metrics2](https://us1.discourse-cdn.com/elastic/original/3X/3/e/3e0ce85ab03ee214df2740d5113eb122f91b6f8c.PNG) logstash metrics ![logstash_metrics1](https://us1.discourse-cdn.com/elastic/original/3X/8/f/8ff7a42f6f8e726b9d6b2d8a0928bb07bda7aaf4.PNG) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [December 14, 2017, 10:18pm UTC](https://discuss.elastic.co/t/elasticsearch-5-3-2-merge-spikes-and-searchability-delay/108031/2 "2017-12-14T22:18:26Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.