# Not enough capacity... why?

**URL:** <https://discuss.elastic.co/t/not-enough-capacity-why/94432>\
**Category:** Elastic Cloud Enterprise (ECE)\
**Created:** [July 25, 2017, 7:31am UTC](https://discuss.elastic.co/t/not-enough-capacity-why/94432 "2017-07-25T07:31:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnnyB](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johnnyb/32/13450_2.png) [@JohnnyB](https://discuss.elastic.co/u/JohnnyB)\
**Post date:** [July 25, 2017, 7:31am UTC](https://discuss.elastic.co/t/not-enough-capacity-why/94432/1 "2017-07-25T07:31:05Z")

</div>

Hi ECE Support team,

I'm trying to allocate clusters on my ECE platform but construtor always tell me that there not enought capacity.

I have a 3 zones plateforme for tests purpose with one in maintenance mode (bat-e one wich hold the cloudUI and the basic ECE services).  
I put it on maintenance since I have problem on that runner and docker (I saw containerID duplicate error message).

Anyway, I'm trying to create a 2 zone clusters. I first asked for 3x16GB + 8 GB dedicated master nodes (which was too much according bat-g available capacity). Then I Asked for 3x4GB + 2 GB dedicated master node then for 3x4GB with no dedicated master node but I still have the same problem :

_Starting step: [allocate-instances]:_  
_instances=List(ElasticsearchInstance(ElasticsearchCluster(ffa7cc500be549efa81343132baf160c),tiebreaker-0000000000), ElasticsearchInstance(ElasticsearchCluster(ffa7cc500be549efa81343132baf160c),instance-0000000001), ElasticsearchInstance(ElasticsearchCluster(ffa7cc500be549efa81343132baf160c),instance-0000000002), ElasticsearchInstance(ElasticsearchCluster(ffa7cc500be549efa81343132baf160c),instance-0000000003), ElasticsearchInstance(ElasticsearchCluster(ffa7cc500be549efa81343132baf160c),instance-0000000004), ElasticsearchInstance(ElasticsearchCluster(ffa7cc500be549efa81343132baf160c),instance-0000000005), ElasticsearchInstance(ElasticsearchCluster(ffa7cc500be549efa81343132baf160c),instance-0000000006)), keepInstances=List()_  
_2017-07-25T07:17:25.322Z_  
_Unexpected error during step: [allocate-instances]: [no.found.constructor.steps.allocation.AllocationFailedException: Allocation failed: [NotEnoughCapacity(6,7,Map(zone-0 -\> 12288, tiebreaker -\> 1024, zone-1 -\> 12288))]]_

Here is the capacity I can see in the UI :

 ![](https://us1.discourse-cdn.com/elastic/original/3X/8/a/8a3914f9a8c597483f5c989ef2b8a2a4d2614e0b.PNG)

What's the problem ? Is it related to maintenance mode ?

I think that the documentation could contains the instance type and count according to the options choosed at the creation of the cluster. It could help.

Regards,  
Johnny

---

<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:** [July 25, 2017, 8:48am UTC](https://discuss.elastic.co/t/not-enough-capacity-why/94432/2 "2017-07-25T08:48:35Z")

</div>

Hello Jonny,  
If I understand correctly, you put the only node in a zone `bat-e` to maintenance mode. Therefore, effectively you have allocators in 2 zones.  
Your ECE cluster fails to create a 2 zone cluster because to create a cluster with this configuration we actually use 3 zones: the 3rd zone is used for `tiebreaker` node.  
As far as I know, there is no way to disable creation of the 'tiebraker' node in the UI.  
If you disable maintenance mode for the node in the zone `bat-e`, the cluster will be created.

---

<div class="post-metadata">

**Author:** ![JohnnyB](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/johnnyb/32/13450_2.png) [@JohnnyB](https://discuss.elastic.co/u/JohnnyB)\
**Post date:** [July 25, 2017, 12:04pm UTC](https://discuss.elastic.co/t/not-enough-capacity-why/94432/3 "2017-07-25T12:04:13Z")

</div>

Hi @Yuri,

Thanks for your answer. You effectively confirm what I supposed.

This is why I propose you to add the topology of cluster created by ECE on the documentation (for each 3 types of fault tolerance)

Johnny.

---

<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:** [July 25, 2017, 12:23pm UTC](https://discuss.elastic.co/t/not-enough-capacity-why/94432/4 "2017-07-25T12:23:15Z")

</div>

@JohnnyB, I totally agree with you, we do need to provide more details about this implicit behavior. We will update the documentation.

Best regards,  
Yuri

---

<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:** [August 8, 2017, 12:23pm UTC](https://discuss.elastic.co/t/not-enough-capacity-why/94432/5 "2017-08-08T12:23:31Z")

</div>

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