# Disk space cosideration for elasticsearch in production

**URL:** <https://discuss.elastic.co/t/disk-space-cosideration-for-elasticsearch-in-production/72825>\
**Category:** Elasticsearch\
**Created:** [January 25, 2017, 9:57pm UTC](https://discuss.elastic.co/t/disk-space-cosideration-for-elasticsearch-in-production/72825 "2017-01-25T21:57:55Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![krishna\_chaitanya](https://avatars.discourse-cdn.com/v4/letter/k/b5a626/32.png) [@krishna\_chaitanya](https://discuss.elastic.co/u/krishna_chaitanya)\
**Post date:** [January 26, 2017, 7:26pm UTC](https://discuss.elastic.co/t/disk-space-cosideration-for-elasticsearch-in-production/72825/6 "2017-01-26T19:26:47Z")

</div>

I have one more question, and this is about how master election is done if I have 3 nodes(2master+data and 1 dedicated master).

I have gone through [this](https://discuss.elastic.co/t/hardware-recommendation/66833/12) post, where you have given some details about using such configuration(3 nodes startup) for small clusters. With 10GB/day and holding 3 TB of index data, I believe my cluster is also a small one. I have also gone through master-election documentation [here](https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-zen.html).

Since I don't want my data nodes to be doing extra work, I would like to have my only dedicated master node to be the actual master. How can I make sure that happens during Master-Election? Or is this the default behavior?

---

_[View the full topic](https://discuss.elastic.co/t/disk-space-cosideration-for-elasticsearch-in-production/72825)._