# How many ES nodes will be needed to handle 400GB/Day Data **URL:** \ **Category:** Elasticsearch\ **Created:** [September 22, 2017, 9:38am UTC](https://discuss.elastic.co/t/how-many-es-nodes-will-be-needed-to-handle-400gb-day-data/101458 "2017-09-22T09:38:49Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![vikas\_gopal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikas_gopal/32/47661_2.png) [@vikas\_gopal](https://discuss.elastic.co/u/vikas_gopal)\ **Post date:** [September 22, 2017, 9:38am UTC](https://discuss.elastic.co/t/how-many-es-nodes-will-be-needed-to-handle-400gb-day-data/101458/1 "2017-09-22T09:38:49Z")
Hi Experts, I know this is not an easy question to answer but still any idea can help here . Curious to know how many ES nodes will be sufficient to handle 400 GB/day data volume . I have gone through this blog([https://www.elastic.co/blog/elasticsearch-storage-the-true-story-2.0](https://www.elastic.co/blog/elasticsearch-storage-the-true-story-2.0) AND ) and this is what my requirement is Sting Fields :- analyzed and not\_analyzed \_all :- disabled No of users :- 70+ Data Type :- Structured Data Storage :- 30 Days Replication factor :- 3 or 4 Search Type;- Users will be opening Dashboards , which will have lots of aggregated data . Regards Vikas ---
**Author:** ![vikas\_gopal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikas_gopal/32/47661_2.png) [@vikas\_gopal](https://discuss.elastic.co/u/vikas_gopal)\ **Post date:** [September 22, 2017, 10:48am UTC](https://discuss.elastic.co/t/how-many-es-nodes-will-be-needed-to-handle-400gb-day-data/101458/2 "2017-09-22T10:48:08Z")
This is what I am planing to have only for ES Total VM for ES cluster :- 8 nodes Total RAM :- 256 GB (32 GB each node ) OS :- Linux 64 bit Dedicates master nodes :- 3 Dedicated Hot Data Node :- 5 For Kibana I am proposing Total VM :- 2 (6 GB RAM + 100 GB hard disk) For LS :- 2 (8 GB RAM + 300 GB Hard Disk) Can someone suggest if this is the acceptable architecture or do I need to modify ? Reagrds VG ---
**Author:** ![Ravi\_Shanker\_Reddy](https://avatars.discourse-cdn.com/v4/letter/r/a5b964/32.png) [@Ravi\_Shanker\_Reddy](https://discuss.elastic.co/u/Ravi_Shanker_Reddy)\ **Post date:** [September 22, 2017, 11:40am UTC](https://discuss.elastic.co/t/how-many-es-nodes-will-be-needed-to-handle-400gb-day-data/101458/3 "2017-09-22T11:40:15Z")
> [@vikas\_gopal](#): > > For LS :- 2 (8 GB RAM + 300 GB Hard Disk) > [@vikas\_gopal](#): > > Total VM :- 2 (6 GB RAM + 100 GB hard disk) These LS and Kibana are not disk hungry. You can utilise this for cold nodes or ES ---
**Author:** ![vikas\_gopal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikas_gopal/32/47661_2.png) [@vikas\_gopal](https://discuss.elastic.co/u/vikas_gopal)\ **Post date:** [September 22, 2017, 11:44am UTC](https://discuss.elastic.co/t/how-many-es-nodes-will-be-needed-to-handle-400gb-day-data/101458/4 "2017-09-22T11:44:30Z")
Thanks @Ravi_Shanker_Reddy for the advice actually that is what my plan is . Moreover I want to store a copy of raw data on LS machine as well . So here cold ES means older data ? here I have question does this mean that this data/node will never take participation during the search even if I increase the tie range ? Also what is your recommendation on ES setup , is that architecture ok ? Regards VG ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 20, 2017, 11:44am UTC](https://discuss.elastic.co/t/how-many-es-nodes-will-be-needed-to-handle-400gb-day-data/101458/5 "2017-10-20T11:44:55Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.