# Upgrade to 1.4.2 from 1.1.1 causes spike in Disk IO **URL:** \ **Category:** Elasticsearch\ **Created:** [February 11, 2015, 4:57pm UTC](https://discuss.elastic.co/t/upgrade-to-1-4-2-from-1-1-1-causes-spike-in-disk-io/22103 "2015-02-11T16:57:10Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![George\_Stathis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/george_stathis/32/918_2.png) [@George\_Stathis](https://discuss.elastic.co/u/George_Stathis)\ **Post date:** [February 11, 2015, 4:57pm UTC](https://discuss.elastic.co/t/upgrade-to-1-4-2-from-1-1-1-causes-spike-in-disk-io/22103/1 "2015-02-11T16:57:10Z")
Hi there, We just completed this past Monday an ES upgrade from 1.1.1 to 1.4.2 and a Java upgrade from 7 to 8. No other changes. Same boxes, same specs, no new queries or filters, no increased requests. What I see in Marvel since the upgrade is a large spike in Disk IO: [https://lh6.googleusercontent.com/-i6OYBiqputk/VNuJC-47eII/AAAAAAAAA\_g/TWxTcres-Uk/s1600/Screen%2BShot%2B2015-02-11%2Bat%2B11.37.58%2BAM.png](https://lh6.googleusercontent.com/-i6OYBiqputk/VNuJC-47eII/AAAAAAAAA_g/TWxTcres-Uk/s1600/Screen%2BShot%2B2015-02-11%2Bat%2B11.37.58%2BAM.png) and a large dip in field data, filter cache and overall index memory consumption: [https://lh5.googleusercontent.com/-2DRu7af1npc/VNuJNqsvOQI/AAAAAAAAA\_o/56trKYYMiQw/s1600/Screen%2BShot%2B2015-02-11%2Bat%2B11.37.47%2BAM.png](https://lh5.googleusercontent.com/-2DRu7af1npc/VNuJNqsvOQI/AAAAAAAAA_o/56trKYYMiQw/s1600/Screen%2BShot%2B2015-02-11%2Bat%2B11.37.47%2BAM.png) Should I be looking at the new circuit breaker [http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-fielddata.html#circuit-breaker](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-fielddata.html#circuit-breaker) settings? Any pointers are welcome! -GS -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/5e6dbf8a-4dd9-46d3-8cdb-a45c79a6b43c%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/5e6dbf8a-4dd9-46d3-8cdb-a45c79a6b43c%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![Boaz\_Leskes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/boaz_leskes/32/723_2.png) [@Boaz\_Leskes](https://discuss.elastic.co/u/Boaz_Leskes)\ **Post date:** [February 15, 2015, 10:28pm UTC](https://discuss.elastic.co/t/upgrade-to-1-4-2-from-1-1-1-causes-spike-in-disk-io/22103/2 "2015-02-15T22:28:16Z")
1.4.2 comes with a couple optimization which might explain the drop in field data cache and lucene memory (most notably here is the disabling of bloom filters by default - due to improvements in lucene they are not as needed as before and we can save on the memory). The IO spike might come from [Cache fileLength for fully written files by s1monw · Pull Request #9683 · elastic/elasticsearch · GitHub](https://github.com/elasticsearch/elasticsearch/pull/9683) , which is still under heavy discussion. Can you try running \_hot\_threads on you cluster and see whether you there's anything stats releated there? On Wednesday, February 11, 2015 at 5:57:11 PM UTC+1, George Stathis wrote: > Hi there, > > We just completed this past Monday an ES upgrade from 1.1.1 to 1.4.2 and a > Java upgrade from 7 to 8. No other changes. Same boxes, same specs, no new > queries or filters, no increased requests. What I see in Marvel since the > upgrade is a large spike in Disk IO: > > [https://lh6.googleusercontent.com/-i6OYBiqputk/VNuJC-47eII/AAAAAAAAA\_g/TWxTcres-Uk/s1600/Screen%2BShot%2B2015-02-11%2Bat%2B11.37.58%2BAM.png](https://lh6.googleusercontent.com/-i6OYBiqputk/VNuJC-47eII/AAAAAAAAA_g/TWxTcres-Uk/s1600/Screen%2BShot%2B2015-02-11%2Bat%2B11.37.58%2BAM.png) > > and a large dip in field data, filter cache and overall index memory > consumption: > > [https://lh5.googleusercontent.com/-2DRu7af1npc/VNuJNqsvOQI/AAAAAAAAA\_o/56trKYYMiQw/s1600/Screen%2BShot%2B2015-02-11%2Bat%2B11.37.47%2BAM.png](https://lh5.googleusercontent.com/-2DRu7af1npc/VNuJNqsvOQI/AAAAAAAAA_o/56trKYYMiQw/s1600/Screen%2BShot%2B2015-02-11%2Bat%2B11.37.47%2BAM.png) > > Should I be looking at the new circuit breaker > [http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-fielddata.html#circuit-breaker](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules-fielddata.html#circuit-breaker) > settings? > > Any pointers are welcome! > > -GS -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/d9ed771b-0c8b-4e32-863b-d33b1cf94da0%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/d9ed771b-0c8b-4e32-863b-d33b1cf94da0%40googlegroups.com). For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 12:32am UTC](https://discuss.elastic.co/t/upgrade-to-1-4-2-from-1-1-1-causes-spike-in-disk-io/22103/3 "2017-07-06T00:32:40Z")