# Machine learning option disabled

**URL:** https://discuss.elastic.co/t/machine-learning-option-disabled/124657
**Category:** Kibana
**Created:** [March 19, 2018, 10:42pm UTC](https://discuss.elastic.co/t/machine-learning-option-disabled/124657 "2018-03-19T22:42:30Z")
**Posts on this page:** 1
**Showing post:** 4

<div class="post-metadata">

### Author: ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)
#### Post date: [March 20, 2018, 2:46am UTC](https://discuss.elastic.co/t/machine-learning-option-disabled/124657/4 "2018-03-20T02:46:18Z")

</div>

Hi Kantimati,

May be when you do a `GET _xpack` you see ML as disbled. Its disabled by default. u need to put `xpack.ml.enabled: true` into a field "User Settings" on the page "Create Cluster".  
You can follow a similar discuss post here to know the reason behind it being disabled by default.

> [@Machine Learning disabled by default?](https://discuss.elastic.co/t/machine-learning-disabled-by-default/99052/4):
>
> 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 recomme…

Hope this helps  
Cheers  
Rashmi

---

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