# IOPS change monitoring

**URL:** <https://discuss.elastic.co/t/iops-change-monitoring/83871>\
**Category:** Elasticsearch\
**Created:** [April 27, 2017, 1:44pm UTC](https://discuss.elastic.co/t/iops-change-monitoring/83871 "2017-04-27T13:44:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![guy\_es](https://avatars.discourse-cdn.com/v4/letter/g/67e7ee/32.png) [@guy\_es](https://discuss.elastic.co/u/guy_es)\
**Post date:** [April 27, 2017, 1:44pm UTC](https://discuss.elastic.co/t/iops-change-monitoring/83871/1 "2017-04-27T13:44:38Z")

</div>

Hi,

I have a 2.4 cluster running on AWS instances.  
I want to lower the disk's IOPS and would like to monitor the affect on the performance of ES.

1. Which operations will be affected from IOPS decrease?
2. How can I monitor the performance decrease (Which end point, which metric)?
3. How will I know the IOPS is to low and the cluster is no longer working good?

Thanks  
Guy

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [April 27, 2017, 2:29pm UTC](https://discuss.elastic.co/t/iops-change-monitoring/83871/2 "2017-04-27T14:29:46Z")

</div>

Indexing always uses the disk. Searching will use the disk if it the files aren't already in the filesystem cache.

The best metric to monitor is metrics from your application like search response time. You should also look for Elasticsearch logging stuff about merging falling behind.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 25, 2017, 2:31pm UTC](https://discuss.elastic.co/t/iops-change-monitoring/83871/3 "2017-05-25T14:31:04Z")

</div>

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