# Memory store changes in elasticsearch 1.7.x **URL:** \ **Category:** Elasticsearch\ **Created:** [September 8, 2015, 11:37pm UTC](https://discuss.elastic.co/t/memory-store-changes-in-elasticsearch-1-7-x/28877 "2015-09-08T23:37:46Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![denpa](https://avatars.discourse-cdn.com/v4/letter/d/51bf81/32.png) [@denpa](https://discuss.elastic.co/u/denpa)\ **Post date:** [September 8, 2015, 11:37pm UTC](https://discuss.elastic.co/t/memory-store-changes-in-elasticsearch-1-7-x/28877/1 "2015-09-08T23:37:46Z")
I am running a 0.90.x cluster using memory store, and i am working towards upgrading to 1.7.x My setup was basically a handful of nodes with a 3GB heap, and memory store makes them write into direct memory outside the heap. When I tried to test the setup on 1.7.x, the memory store seems to write it into the heap, which is definitely not preferred due to inefficient storage, garbage collection impact, and the java compressed pointers deal. Is there a configuration to set it to write to Direct Memory like before? OS: Windows Server 2012 ---
**Author:** ![javanna](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/javanna/32/4698_2.png) [@javanna](https://discuss.elastic.co/u/javanna)\ **Post date:** [September 10, 2015, 5:14pm UTC](https://discuss.elastic.co/t/memory-store-changes-in-elasticsearch-1-7-x/28877/2 "2015-09-10T17:14:43Z")
Not that I know of, also beware that memory store is removed in 2.0.beta1 already. You might want to look into using ordinary store instead, have a look at [https://github.com/elastic/elasticsearch/pull/8536](https://github.com/elastic/elasticsearch/pull/8536) for the removal PR. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 5, 2017, 11:51pm UTC](https://discuss.elastic.co/t/memory-store-changes-in-elasticsearch-1-7-x/28877/3 "2017-07-05T23:51:07Z")