# What is the shard recommendation for 3 master nodes, 2 data nodes cluster

**URL:** <https://discuss.elastic.co/t/what-is-the-shard-recommendation-for-3-master-nodes-2-data-nodes-cluster/149151>\
**Category:** Elasticsearch\
**Created:** [September 19, 2018, 4:03pm UTC](https://discuss.elastic.co/t/what-is-the-shard-recommendation-for-3-master-nodes-2-data-nodes-cluster/149151 "2018-09-19T16:03:57Z")\
**Posts on this page:** 10\
**Page:** 1

<div class="post-metadata">

**Author:** ![rajkumar.m](https://avatars.discourse-cdn.com/v4/letter/r/e9bcb4/32.png) [@rajkumar.m](https://discuss.elastic.co/u/rajkumar.m)\
**Post date:** [September 19, 2018, 4:03pm UTC](https://discuss.elastic.co/t/what-is-the-shard-recommendation-for-3-master-nodes-2-data-nodes-cluster/149151/1 "2018-09-19T16:03:57Z")

</div>

Hi Team,

what is the shard recommendation for 3 master nodes, 2 data nodes cluster?  
Please advise, how it will impact performance and  
if we have 1 shard per index, will it impact resiliency of data.

Thanks in Advance.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 19, 2018, 4:27pm UTC](https://discuss.elastic.co/t/what-is-the-shard-recommendation-for-3-master-nodes-2-data-nodes-cluster/149151/2 "2018-09-19T16:27:56Z")

</div>

What is the use case?

---

<div class="post-metadata">

**Author:** ![rajkumar.m](https://avatars.discourse-cdn.com/v4/letter/r/e9bcb4/32.png) [@rajkumar.m](https://discuss.elastic.co/u/rajkumar.m)\
**Post date:** [September 19, 2018, 4:43pm UTC](https://discuss.elastic.co/t/what-is-the-shard-recommendation-for-3-master-nodes-2-data-nodes-cluster/149151/3 "2018-09-19T16:43:44Z")

</div>

Thanks for response Christian !!

after upgrade from elk4 to 5, I found that default sharding was set to 5.  
I found performance issues after upgrade. and I am trying optimize and changed the value to 1 shard in index template.  
but I would like to see the impact of using the 1 Shard Vs 5 shards.  
Please advise

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 19, 2018, 4:47pm UTC](https://discuss.elastic.co/t/what-is-the-shard-recommendation-for-3-master-nodes-2-data-nodes-cluster/149151/4 "2018-09-19T16:47:54Z")

</div>

What is the use case? Are you using time-based indices? How much data do you have?

---

<div class="post-metadata">

**Author:** ![rajkumar.m](https://avatars.discourse-cdn.com/v4/letter/r/e9bcb4/32.png) [@rajkumar.m](https://discuss.elastic.co/u/rajkumar.m)\
**Post date:** [September 19, 2018, 5:20pm UTC](https://discuss.elastic.co/t/what-is-the-shard-recommendation-for-3-master-nodes-2-data-nodes-cluster/149151/5 "2018-09-19T17:20:14Z")

</div>

i am not using time-based events. i am sending data to elastic data node through API  
i am sending data 2G per day and creating new index per month.  
is sharding depends on the data or number of nodes in cluster? please advise

---

<div class="post-metadata">

**Author:** ![rajkumar.m](https://avatars.discourse-cdn.com/v4/letter/r/e9bcb4/32.png) [@rajkumar.m](https://discuss.elastic.co/u/rajkumar.m)\
**Post date:** [September 20, 2018, 9:42pm UTC](https://discuss.elastic.co/t/what-is-the-shard-recommendation-for-3-master-nodes-2-data-nodes-cluster/149151/6 "2018-09-20T21:42:11Z")

</div>

if we use 1 shard per index, how it is impacting the resiliency of data.  
i have 2 data nodes with 1 replica setting, please help

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 21, 2018, 4:43am UTC](https://discuss.elastic.co/t/what-is-the-shard-recommendation-for-3-master-nodes-2-data-nodes-cluster/149151/7 "2018-09-21T04:43:51Z")

</div>

If you have 2 data nodes and have all indices configured to have 1 replica, both data nodes will hold all data. This means you can continue operating even if one of the nodes go down.

---

<div class="post-metadata">

**Author:** ![rajkumar.m](https://avatars.discourse-cdn.com/v4/letter/r/e9bcb4/32.png) [@rajkumar.m](https://discuss.elastic.co/u/rajkumar.m)\
**Post date:** [September 21, 2018, 5:00am UTC](https://discuss.elastic.co/t/what-is-the-shard-recommendation-for-3-master-nodes-2-data-nodes-cluster/149151/8 "2018-09-21T05:00:30Z")

</div>

sorry!! i am confused with Sharding.  
is sharding number impacts resiliency of data?  
and how sharding is impacts performance, because i could see lot of performance issues in my cluster after upgrade. please advsie

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [September 21, 2018, 7:00am UTC](https://discuss.elastic.co/t/what-is-the-shard-recommendation-for-3-master-nodes-2-data-nodes-cluster/149151/9 "2018-09-21T07:00:29Z")

</div>

Even though it was written for Elasticsearch 2.x, [Elasticsearch - the Definitive Guide](https://www.elastic.co/guide/en/elasticsearch/guide/current/distributed-cluster.html) still describes the roles of shards and indices quite well.

---

<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:** [October 19, 2018, 7:00am UTC](https://discuss.elastic.co/t/what-is-the-shard-recommendation-for-3-master-nodes-2-data-nodes-cluster/149151/10 "2018-10-19T07:00:33Z")

</div>

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