# Total\_shards\_per\_node leading to unassigned shards

**URL:** <https://discuss.elastic.co/t/total-shards-per-node-leading-to-unassigned-shards/14680>\
**Category:** Elasticsearch\
**Created:** [December 3, 2013, 3:14pm UTC](https://discuss.elastic.co/t/total-shards-per-node-leading-to-unassigned-shards/14680 "2013-12-03T15:14:27Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andrew\_Ochsner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_ochsner/32/1287_2.png) [@Andrew\_Ochsner](https://discuss.elastic.co/u/Andrew_Ochsner)\
**Post date:** [December 3, 2013, 3:14pm UTC](https://discuss.elastic.co/t/total-shards-per-node-leading-to-unassigned-shards/14680/1 "2013-12-03T15:14:27Z")

</div>

Hello:

I'm running 0.90.0 in a 3 node cluster. I have number\_of\_shards = 3 and  
number\_of\_replicas = 1. Recently I set total\_shards\_per\_node = 2 so that I  
could 1) ensure when I lose a node, ES doesn't try to rebalance on the  
remaining 2 nodes (I don't have the disk space as I found out earlier) and  
2) ensure uniform distribution of the shards. If there's a better way to  
meet 1) then I'm all for it.

Unfortunately what I'm seeing occasionally is this... "stuck" allocations  
where replica 2 doesn't have anywhere to go so I have to manually move 0 or  
1 to make room.  
[https://lh4.googleusercontent.com/-Fed1RYUfjYE/Up31CYLpf3I/AAAAAAAABBI/bS6L7-0w87Q/s1600/2013-12-03+09\_12\_36-ElasticSearch+Head.png](https://lh4.googleusercontent.com/-Fed1RYUfjYE/Up31CYLpf3I/AAAAAAAABBI/bS6L7-0w87Q/s1600/2013-12-03+09_12_36-ElasticSearch+Head.png)

Is this fixed in a later version? Or a known issue? How can I help?

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/f9bf7e9f-2981-403a-b8b5-7fe784c1b422%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/f9bf7e9f-2981-403a-b8b5-7fe784c1b422%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Andrew\_Ochsner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_ochsner/32/1287_2.png) [@Andrew\_Ochsner](https://discuss.elastic.co/u/Andrew_Ochsner)\
**Post date:** [December 10, 2013, 2:36pm UTC](https://discuss.elastic.co/t/total-shards-per-node-leading-to-unassigned-shards/14680/2 "2013-12-10T14:36:49Z")

</div>

Anyone?

On Tuesday, December 3, 2013 9:14:27 AM UTC-6, Andrew Ochsner wrote:

> Hello:
> 
> I'm running 0.90.0 in a 3 node cluster. I have number\_of\_shards = 3 and  
> number\_of\_replicas = 1. Recently I set total\_shards\_per\_node = 2 so that I  
> could 1) ensure when I lose a node, ES doesn't try to rebalance on the  
> remaining 2 nodes (I don't have the disk space as I found out earlier) and  
> 2) ensure uniform distribution of the shards. If there's a better way to  
> meet 1) then I'm all for it.
> 
> Unfortunately what I'm seeing occasionally is this... "stuck" allocations  
> where replica 2 doesn't have anywhere to go so I have to manually move 0 or  
> 1 to make room.
> 
> [https://lh4.googleusercontent.com/-Fed1RYUfjYE/Up31CYLpf3I/AAAAAAAABBI/bS6L7-0w87Q/s1600/2013-12-03+09\_12\_36-ElasticSearch+Head.png](https://lh4.googleusercontent.com/-Fed1RYUfjYE/Up31CYLpf3I/AAAAAAAABBI/bS6L7-0w87Q/s1600/2013-12-03+09_12_36-ElasticSearch+Head.png)
> 
> Is this fixed in a later version? Or a known issue? How can I help?

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/9dcd0e85-945a-44b4-8da0-69868d464322%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/9dcd0e85-945a-44b4-8da0-69868d464322%40googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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 6, 2017, 2:02am UTC](https://discuss.elastic.co/t/total-shards-per-node-leading-to-unassigned-shards/14680/3 "2017-07-06T02:02:13Z")

</div>


