# Elasticsearch Helm chart- node type clarification

**URL:** <https://discuss.elastic.co/t/elasticsearch-helm-chart-node-type-clarification/272803>\
**Category:** Elasticsearch\
**Created:** [May 12, 2021, 11:46am UTC](https://discuss.elastic.co/t/elasticsearch-helm-chart-node-type-clarification/272803 "2021-05-12T11:46:14Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mrudrego](https://avatars.discourse-cdn.com/v4/letter/m/898d66/32.png) [@mrudrego](https://discuss.elastic.co/u/mrudrego)\
**Post date:** [May 12, 2021, 11:46am UTC](https://discuss.elastic.co/t/elasticsearch-helm-chart-node-type-clarification/272803/1 "2021-05-12T11:46:14Z")

</div>

Hi,  
With the default Elasticsearch helm charts configuration all elasticsearch pods plays all roles(master,data, client). Also there is example configuration for setting different roles.

Wanted to understand which is the best solution in production, is it to deploy with all pods playing all roles or having pods with specific roles ?

If we use the solution of all pods performing all roles, can you please help to know how to we scale the pods when there is more requests or want to store more data. By scaling the pods, it would also indirectly have the same number of masters as the number of pod replicas. But have read some blogs which suggests to have odd number of masters to prevent brain split issues in cluster.

Please help with the above queries.

Thanks in advance.

---

<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:** [June 9, 2021, 11:46am UTC](https://discuss.elastic.co/t/elasticsearch-helm-chart-node-type-clarification/272803/2 "2021-06-09T11:46:59Z")

</div>

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