# Increased memory not detected by Allocator

**URL:** <https://discuss.elastic.co/t/increased-memory-not-detected-by-allocator/91060>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [June 28, 2017, 8:00am UTC](https://discuss.elastic.co/t/increased-memory-not-detected-by-allocator/91060 "2017-06-28T08:00:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Niklas](https://avatars.discourse-cdn.com/v4/letter/n/34f0e0/32.png) [@Niklas](https://discuss.elastic.co/u/Niklas)\
**Post date:** [June 28, 2017, 8:00am UTC](https://discuss.elastic.co/t/increased-memory-not-detected-by-allocator/91060/1 "2017-06-28T08:00:52Z")

</div>

Hi. We are trying ECE out and I installed it on a Redhat 7 with 16 GB. of memory.. We played around a bit, creating clusters e.g but 16GB does not fit that many clusters.  
So we installed 32 GB in the server.  
The allocator still shows a total capacity of 11.96 GB and I get "Unexpected error during step: [allocate-instances]: [no.found.constructor.steps.allocation.AllocationFailedException: Allocation failed: [NotEnoughCapacity(0,1,Map(zone-0 -\> 2048))]]" when trying to start up an elastic with 2 GB on the allocator showing less than 1 GB free.

The free command on the OS shows 6.9 GB free memory.

Does anyone knows how to "refresh" the allocator to see the new memory size?

Running ECE 1.0.0

---

<div class="post-metadata">

**Author:** ![Yuri](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yuri/32/52458_2.png) [@Yuri](https://discuss.elastic.co/u/Yuri)\
**Post date:** [June 28, 2017, 1:22pm UTC](https://discuss.elastic.co/t/increased-memory-not-detected-by-allocator/91060/2 "2017-06-28T13:22:46Z")

</div>

Hi Niklas,

I am not sure that we currently support allocator capacity changing.  
However, you can use the following strategy:

1. Vacate allocator. See [Move Nodes From Allocators](https://www.elastic.co/guide/en/cloud-enterprise/1.0.0/ece-move-nodes.html)
2. Delete runner. See [Delete Runner](https://www.elastic.co/guide/en/cloud-enterprise/1.0.0/ece-delete-runner.html)
3. Remove all docker containers (ECE container's name starts with 'frc-') from the host
4. Install ECE node. See [Install on Additional Hosts](https://www.elastic.co/guide/en/cloud-enterprise/1.0.0/ece-installing.html#ece-installing-additional)

By default, the installer allocates 85% of available RAM for Elasticsearch clusters, but you can override this value. See [Installer Script Reference](https://www.elastic.co/guide/en/cloud-enterprise/1.0.0/ece-installation-script.html#ece-installation-script) and argument `--capacity` in particular.

PS This will work if your ECE cluster has more than one node and there is enough capacity on other nodes to accommodate clusters from the node you want to upgrade.

---

<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:** [July 12, 2017, 1:22pm UTC](https://discuss.elastic.co/t/increased-memory-not-detected-by-allocator/91060/3 "2017-07-12T13:22:53Z")

</div>

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