# Specifics for Disabling Allocation Awareness Dynamically

**URL:** <https://discuss.elastic.co/t/specifics-for-disabling-allocation-awareness-dynamically/56010>\
**Category:** Elasticsearch\
**Created:** [July 20, 2016, 5:57pm UTC](https://discuss.elastic.co/t/specifics-for-disabling-allocation-awareness-dynamically/56010 "2016-07-20T17:57:16Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Caleb\_Phillips](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/caleb_phillips/32/1540_2.png) [@Caleb\_Phillips](https://discuss.elastic.co/u/Caleb_Phillips)\
**Post date:** [July 20, 2016, 5:57pm UTC](https://discuss.elastic.co/t/specifics-for-disabling-allocation-awareness-dynamically/56010/1 "2016-07-20T17:57:16Z")

</div>

This page [Cluster | Elasticsearch Guide [1.5] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/1.5/modules-cluster.html) says that allocation awareness "settings can be updated using the cluster update settings API on a live cluster."

If I have settings like these from that page:

> cluster.routing.allocation.awareness.force.zone.values: zone1,zone2  
> cluster.routing.allocation.awareness.attributes: zone

Do I put empty strings to those keys when I update the cluster settings?

Thanks

---

<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:** [July 5, 2017, 10:33pm UTC](https://discuss.elastic.co/t/specifics-for-disabling-allocation-awareness-dynamically/56010/2 "2017-07-05T22:33:58Z")

</div>