# Architecture Design

**URL:** <https://discuss.elastic.co/t/architecture-design/164837>\
**Category:** Elasticsearch\
**Created:** [January 18, 2019, 4:57pm UTC](https://discuss.elastic.co/t/architecture-design/164837 "2019-01-18T16:57:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Miguel\_Leite](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/miguel_leite/32/41988_2.png) [@Miguel\_Leite](https://discuss.elastic.co/u/Miguel_Leite)\
**Post date:** [January 18, 2019, 4:57pm UTC](https://discuss.elastic.co/t/architecture-design/164837/1 "2019-01-18T16:57:02Z")

</div>

Hey guys!!

I'm trying to understand how to scale my ELK setup to a production deployment... But first some specs on my current system:

- Multiple Servers where I'm fetching data with Filebeat (around 10gb/day of logs)
- One central server with Elasticsearch, Kibana and Logstash with: 32GB RAM, 500GB memory disk, 4 processing cores;

So basically I just have one node on my system.

But in order to scale it up to A LOT of more servers I'm trying to understand what kind of hardware requirements I need, for:

- 100GB/day of log files
- Dashboards usage
- Retention period of two months

From the reading I've done all over the internet, I would have:

- 3 Master Nodes
- 3 Data Nodes, for storing all that data

Does this make any sense?? What kind of hardware requirements do I need in each node?? Also, in this case, each node means a server/VM, right??

Thanks a lot! All help would be highly appreciated... Just trying to understand this hardware area of the Elastic Stack, and it has not been easy!!

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [January 18, 2019, 5:08pm UTC](https://discuss.elastic.co/t/architecture-design/164837/2 "2019-01-18T17:08:37Z")

</div>

May I suggest you look at the following resources about sizing:

[https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing](https://www.elastic.co/elasticon/conf/2016/sf/quantitative-cluster-sizing)

> **[How many shards should I have in my Elasticsearch cluster?
	  	 | Elastic](https://www.elastic.co/blog/how-many-shards-should-i-have-in-my-elasticsearch-cluster)**
>
> Elasticsearch is a very versatile platform, that supports a variety of use cases, and provides great flexibility around data organisation and replication strategies. This flexibility can however somet...

> **[NetSecureDay: Managing your Black Friday Logs](https://speakerdeck.com/elastic/netsecureday-managing-your-black-friday-logs)**
>
> Surveiller une application complexe n’est pas une tâche aisée, mais avec les bons outils, ce n’est pas si sorcier. Néanmoins, des périodes fortes telles que les opérations de type « Black Friday » (Vendredi noir) ou période de Noël peuvent pousser...

And [https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right](https://www.elastic.co/webinars/using-rally-to-get-your-elasticsearch-cluster-size-right)

---

<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:** [February 15, 2019, 5:08pm UTC](https://discuss.elastic.co/t/architecture-design/164837/3 "2019-02-15T17:08:39Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.