# Elastic search using a lot of memory, GC thrashing

**URL:** <https://discuss.elastic.co/t/elastic-search-using-a-lot-of-memory-gc-thrashing/48695>\
**Category:** Elasticsearch\
**Created:** [April 28, 2016, 2:52pm UTC](https://discuss.elastic.co/t/elastic-search-using-a-lot-of-memory-gc-thrashing/48695 "2016-04-28T14:52:56Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [May 2, 2016, 11:46am UTC](https://discuss.elastic.co/t/elastic-search-using-a-lot-of-memory-gc-thrashing/48695/2 "2016-05-02T11:46:10Z")

</div>

Hi,

thanks for your analysis! You don't write which version of Elasticsearch you use but it is possible that we fixed the problem in the meantime. So, I suggest that you try to upgrade to the latest possible version first on a test instance and see if the problem persists.

In case it persists, it would be great if you could strip down your scenario so we can reproduce it and then create a ticket on Github.

Daniel

---

_[View the full topic](https://discuss.elastic.co/t/elastic-search-using-a-lot-of-memory-gc-thrashing/48695)._