# ElasticSearch timeouts after upgrade to 6.5.1

**URL:** <https://discuss.elastic.co/t/elasticsearch-timeouts-after-upgrade-to-6-5-1/160235>\
**Category:** Elasticsearch\
**Created:** [December 10, 2018, 7:12pm UTC](https://discuss.elastic.co/t/elasticsearch-timeouts-after-upgrade-to-6-5-1/160235 "2018-12-10T19:12:33Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\
**Post date:** [December 11, 2018, 6:34pm UTC](https://discuss.elastic.co/t/elasticsearch-timeouts-after-upgrade-to-6-5-1/160235/7 "2018-12-11T18:34:13Z")

</div>

> [@devops\_mike](#):
>
> David, I just realized my jvm options were set to automatically create a dump on out of memory error!

Oh yes, I forgot that Elasticsearch sets that by default. You could try opening the heap dump locally and seeing if it looks [similar to this one](https://discuss.elastic.co/t/post-upgrade-issues-6-4-2-es-heap-running-away-6-5-0-too/151096/24) - lots of instances of `OptOutQueryCache` taking up all the space.

However, 6.5.3 is now released, so rather than wading into a heap dump I think it'd be better to try and upgrade and see if it is the problem that I guessed it might be that is now resolved.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-timeouts-after-upgrade-to-6-5-1/160235)._