# Best Cluster Concept, Timeseries Data and more

**URL:** <https://discuss.elastic.co/t/best-cluster-concept-timeseries-data-and-more/241482>\
**Category:** Elasticsearch\
**Tags:** ilm-index-lifecycle-management\
**Created:** [July 16, 2020, 2:23pm UTC](https://discuss.elastic.co/t/best-cluster-concept-timeseries-data-and-more/241482 "2020-07-16T14:23:10Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [July 17, 2020, 9:27am UTC](https://discuss.elastic.co/t/best-cluster-concept-timeseries-data-and-more/241482/4 "2020-07-17T09:27:43Z")

</div>

20GB a day is not a lot of data so I would expect a simple 3-node cluster where all nodes hold data and are master eligible to handle that. There should be no need for dedicated master nodes unless you need to add nodes to get more storage.

For larger volumes it often depends on the relation between indexed volume and retention, e.g. how fast your data turn over.

---

_[View the full topic](https://discuss.elastic.co/t/best-cluster-concept-timeseries-data-and-more/241482)._