# Best way to have a big cluster on a huge bare metal

**URL:** <https://discuss.elastic.co/t/best-way-to-have-a-big-cluster-on-a-huge-bare-metal/217805>\
**Category:** Elasticsearch\
**Created:** [February 4, 2020, 12:42pm UTC](https://discuss.elastic.co/t/best-way-to-have-a-big-cluster-on-a-huge-bare-metal/217805 "2020-02-04T12:42:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Arman\_Ajdani](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/arman_ajdani/32/47196_2.png) [@Arman\_Ajdani](https://discuss.elastic.co/u/Arman_Ajdani)\
**Post date:** [February 4, 2020, 12:42pm UTC](https://discuss.elastic.co/t/best-way-to-have-a-big-cluster-on-a-huge-bare-metal/217805/1 "2020-02-04T12:42:12Z")

</div>

Suppose I have a bare metal with a huge amount of RAM, What is the best approach to have a cluster of ES node, using VM? Multiple instances on different ports? or use an orchestration like Kubernetes? I need a cluster for index speed tune for a huge amount of log. I appreciate it if you point me to good docs.

---

<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:** [March 3, 2020, 12:42pm UTC](https://discuss.elastic.co/t/best-way-to-have-a-big-cluster-on-a-huge-bare-metal/217805/2 "2020-03-03T12:42:18Z")

</div>

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