# ELK Sizing recommendations for Log monitoring?

**URL:** <https://discuss.elastic.co/t/elk-sizing-recommendations-for-log-monitoring/237020>\
**Category:** Elasticsearch\
**Created:** [June 14, 2020, 11:32am UTC](https://discuss.elastic.co/t/elk-sizing-recommendations-for-log-monitoring/237020 "2020-06-14T11:32:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vikas\_mahajan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vikas_mahajan/32/70202_2.png) [@vikas\_mahajan](https://discuss.elastic.co/u/vikas_mahajan)\
**Post date:** [June 14, 2020, 11:32am UTC](https://discuss.elastic.co/t/elk-sizing-recommendations-for-log-monitoring/237020/1 "2020-06-14T11:32:19Z")

</div>

![Sizing](https://us1.discourse-cdn.com/elastic/original/3X/1/4/14aafb1423ceda9a08fb8bb22122d6ffdb679362.jpeg)

Calling out ELK experts to review my design.

1. Do you recommend doubling the no. of shards from 4 to 8 for each index ?
2. One dedicated master node (having 2TB, 256 GB and 16 CPU) will suffice the purpose for managing entire cluster or should i pull out 2 - 3 small VMs out of 5 nodes and dedicate to master node ?
3. Do you recommend Data + ML on the same node ?
4. Client node should be dedicated

Thanks  
Vikas Mahajan

---

<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 12, 2020, 11:38pm UTC](https://discuss.elastic.co/t/elk-sizing-recommendations-for-log-monitoring/237020/2 "2020-07-12T23:38:25Z")

</div>

Closed on July 12, 2020, 11:38pm UTC

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