# Machine Learning disabled by default?

**URL:** https://discuss.elastic.co/t/machine-learning-disabled-by-default/99052
**Category:** Elastic Cloud Enterprise (ECE)
**Created:** [August 31, 2017, 8:30pm UTC](https://discuss.elastic.co/t/machine-learning-disabled-by-default/99052 "2017-08-31T20:30:08Z")
**Posts on this page:** 1
**Showing post:** 4

<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: [September 1, 2017, 3:21pm UTC](https://discuss.elastic.co/t/machine-learning-disabled-by-default/99052/4 "2017-09-01T15:21:07Z")

</div>

ML is disabled for a few reasons:

- One of them is that it is not fully supported by the platform. For example, I do not recommend to create clusters with enabled ML using a topology with 2 availability zones (you should use either 1 or 3 AZ) because in this particular case we create a thin tiebreaker node to support the cluster's quorum. ML job can end up on that node and that can cause its failure.
- Another reason is that we want a user to make a conscious choice. For example, we highly recommend having a dedicated cluster with enabled ML because machine learning process is quite greedy for resources.

Also, we have a great blog post about planning ML for production: [Sizing for Machine Learning with Elasticsearch](https://www.elastic.co/blog/sizing-machine-learning-with-elasticsearch)

---

_[View the full topic](https://discuss.elastic.co/t/machine-learning-disabled-by-default/99052)._