# No ML nodes with sufficient capacity

**URL:** <https://discuss.elastic.co/t/no-ml-nodes-with-sufficient-capacity/303150>\
**Category:** Kibana\
**Tags:** elastic-stack-machine-learning\
**Created:** [April 25, 2022, 10:57am UTC](https://discuss.elastic.co/t/no-ml-nodes-with-sufficient-capacity/303150 "2022-04-25T10:57:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![S-elk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s-elk/32/98464_2.png) [@S-elk](https://discuss.elastic.co/u/S-elk)\
**Post date:** [April 25, 2022, 10:57am UTC](https://discuss.elastic.co/t/no-ml-nodes-with-sufficient-capacity/303150/1 "2022-04-25T10:57:53Z")

</div>

Hello !

I am trying to create a job that handles a large amount of information and the recommended memory is 19 GB. I currently have 2 ml nodes with 64gb each. When executing the job with that memory, the following error appears:

`Could not open job because no ML nodes with sufficient capacity were found`

Any recommendation or solution to this? It would be a great help.

Thanks in advanced!

---

<div class="post-metadata">

**Author:** ![richcollier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/richcollier/32/115035_2.png) [@richcollier](https://discuss.elastic.co/u/richcollier)\
**Post date:** [April 25, 2022, 12:14pm UTC](https://discuss.elastic.co/t/no-ml-nodes-with-sufficient-capacity/303150/2 "2022-04-25T12:14:58Z")

</div>

First and foremost, an ML job only runs on one node at a time so having multiple nodes is irrelevant in the case of a single, massive job. Secondly, by default an ML node will allocate 30% of the node's memory to ML operations (see `xpack.ml.max_machine_memory_percent` in [the docs](https://www.elastic.co/guide/en/elasticsearch/reference/current/ml-settings.html)). So, 30% of 64GB is literally 19.2GB so you're on the hairy edge.

If you self-manage your ML nodes you can modify the above setting but I must ask what your use case is to result in a job memory demand that is that big? This sounds like you're attempting to individually model 600k+ entities all in one job. This is not a good idea and you should consider a different approach and/or breaking the data up into smaller, more manageable portions.

---

<div class="post-metadata">

**Author:** ![S-elk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/s-elk/32/98464_2.png) [@S-elk](https://discuss.elastic.co/u/S-elk)\
**Post date:** [April 26, 2022, 7:27am UTC](https://discuss.elastic.co/t/no-ml-nodes-with-sufficient-capacity/303150/3 "2022-04-26T07:27:40Z")

</div>

Hello.

I was finally able to start the job with the changes you told me but now i have some job with the next warning :

![image](https://us1.discourse-cdn.com/elastic/original/3X/6/f/6f10be14513c2c88173becff4b37572f81b64897.png)

i stop, close and reset the jobs but it keeps coming out.

any solution ?

---

<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:** [May 24, 2022, 7:28am UTC](https://discuss.elastic.co/t/no-ml-nodes-with-sufficient-capacity/303150/4 "2022-05-24T07:28:18Z")

</div>

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