# Shard allocation for logstash **URL:** \ **Category:** Elasticsearch\ **Created:** [October 19, 2013, 11:21pm UTC](https://discuss.elastic.co/t/shard-allocation-for-logstash/14030 "2013-10-19T23:21:59Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Bruce\_Lysik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bruce_lysik/32/2037_2.png) [@Bruce\_Lysik](https://discuss.elastic.co/u/Bruce_Lysik)\ **Post date:** [October 19, 2013, 11:21pm UTC](https://discuss.elastic.co/t/shard-allocation-for-logstash/14030/1 "2013-10-19T23:21:59Z")
Hi, Say I have 6 elastic search data nodes. I want to set my index template to 6 shards, with 2 replicas. Then I will set max shards per node to 3, so I split the index evenly amongst the 6 nodes. However, if there any way to say something like: maximum primary shards: 1 ? What I see now, is that some nodes only end up with replicas. I'd like for each node to have 1 primary, and 2 replicas. Is this possible without doing it manually? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\ **Post date:** [October 20, 2013, 8:05am UTC](https://discuss.elastic.co/t/shard-allocation-for-logstash/14030/2 "2013-10-20T08:05:01Z")
have a look at [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html#_balanced_shards) yet, I wonder if this is really needed since a primary is really just a boolean value on a node metadata that causes an operation to be exected on that shard first. The load should be the same on all node no matter if they have primaries or replicas simon On Sunday, October 20, 2013 1:21:59 AM UTC+2, Bruce Lysik wrote: > Hi, > > Say I have 6 Elasticsearch data nodes. > > I want to set my index template to 6 shards, with 2 replicas. Then I will > set max shards per node to 3, so I split the index evenly amongst the 6 > nodes. > > However, if there any way to say something like: maximum primary shards: 1 > ? > > What I see now, is that some nodes only end up with replicas. I'd like > for each node to have 1 primary, and 2 replicas. > > Is this possible without doing it manually? -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Bruce\_Lysik](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bruce_lysik/32/2037_2.png) [@Bruce\_Lysik](https://discuss.elastic.co/u/Bruce_Lysik)\ **Post date:** [October 20, 2013, 4:55pm UTC](https://discuss.elastic.co/t/shard-allocation-for-logstash/14030/3 "2013-10-20T16:55:04Z")
On Sunday, October 20, 2013 1:05:01 AM UTC-7, simonw wrote: > have a look at > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html#_balanced_shards) > > yet, I wonder if this is really needed since a primary is really just a > boolean value on a node metadata that causes an operation to be exected on > that shard > first. The load should be the same on all node no matter if they have > primaries or replicas So you're saying that in my setup for logstash, as long as every node has the same number of today's shards, the load will be the same on each node? If that's the case, then yes, I wouldn't bother tweaking any further. -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\ **Post date:** [October 20, 2013, 5:22pm UTC](https://discuss.elastic.co/t/shard-allocation-for-logstash/14030/4 "2013-10-20T17:22:02Z")
On Sunday, October 20, 2013 6:55:04 PM UTC+2, Bruce Lysik wrote: > On Sunday, October 20, 2013 1:05:01 AM UTC-7, simonw wrote: > > > have a look at > > [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/cluster-update-settings.html#_balanced_shards) > > > > yet, I wonder if this is really needed since a primary is really just a > > boolean value on a node metadata that causes an operation to be exected on > > that shard > > first. The load should be the same on all node no matter if they have > > primaries or replicas > > So you're saying that in my setup for logstash, as long as every node has > the same number of today's shards, the load will be the same on each node? > If that's the case, then yes, I wouldn't bother tweaking any further. so the responsibility of a primary is to execute the index operation first before it's send to the replicas but eventually everybody does the same work at some point. So I wouldn't worry too much. That is also the reason why we don't bother distribute them in a balanced fashion but rather try to place even number of shards globally and per index on the nodes. It's really just a tie-breaker in the balance algorithm -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:11am UTC](https://discuss.elastic.co/t/shard-allocation-for-logstash/14030/5 "2017-07-06T02:11:32Z")