# ML is available but not enabled

**URL:** https://discuss.elastic.co/t/ml-is-available-but-not-enabled/181357
**Category:** Elasticsearch
**Tags:** elastic-stack-machine-learning
**Created:** [May 16, 2019, 9:50am UTC](https://discuss.elastic.co/t/ml-is-available-but-not-enabled/181357 "2019-05-16T09:50:22Z")
**Posts on this page:** 1
**Showing post:** 4

<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: [May 16, 2019, 7:54pm UTC](https://discuss.elastic.co/t/ml-is-available-but-not-enabled/181357/4 "2019-05-16T19:54:55Z")

</div>

Please refer to:

> [@Separate machine learning node configs](https://discuss.elastic.co/t/separate-machine-learning-node-configs/145201):
>
> Hello i have a 3 node cluster up and running and on all the nodes node.ml is set to "false".Now i want to include a extra node into cluster which will only perform machine learning jobs. As far as my understanding node.ml is to make the node as machine learning node and xpack.ml.enabled is to make the node to perform machine learning jobs. SO setting the node.ml true for one node which is the new node i am introducing and xpack.ml.enabled true on all nodes should make the cluster with one ml no…

In that post you should see that:

> `xpack.ml.enable` should be true on all nodes as it is required for the nodes to talk 'ml' to each other. `node.ml` should only be set on the node you want the machine learning jobs to run on.

Seems like you should set `xpack.ml.enable` to be true on all nodes and then only set `node.ml` to be `true` on `db5`

---

_[View the full topic](https://discuss.elastic.co/t/ml-is-available-but-not-enabled/181357)._