# Unassigned Node and shards

**URL:** <https://discuss.elastic.co/t/unassigned-node-and-shards/19332>\
**Category:** Elasticsearch\
**Created:** [August 18, 2014, 8:29pm UTC](https://discuss.elastic.co/t/unassigned-node-and-shards/19332 "2014-08-18T20:29:56Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![IronMike](https://avatars.discourse-cdn.com/v4/letter/i/e9a140/32.png) [@IronMike](https://discuss.elastic.co/u/IronMike)\
**Post date:** [August 18, 2014, 8:29pm UTC](https://discuss.elastic.co/t/unassigned-node-and-shards/19332/1 "2014-08-18T20:29:56Z")

</div>

I saw this problem twice now.  
I start with a Green two-node cluster, default 5 shards/node, I index about  
50,000 docs, shards/replicas look great and well balanced across the 2  
nodes.

I try the same test with 8 million docs. I come back when its done, and I  
see all primary shards on node1 and 2 replicas on node2 and three  
unassigned replicas on a third "unassigned" node.

I will look through the logs, but I was wondering if anyone has seen  
something similar or has any idea where/why this is coming from before I  
dig?

--  
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/2bddca5e-ea3d-4804-9a0d-47d98bab96c1%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2bddca5e-ea3d-4804-9a0d-47d98bab96c1%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![jprante](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jprante/32/44941_2.png) [@jprante](https://discuss.elastic.co/u/jprante)\
**Post date:** [August 18, 2014, 9:56pm UTC](https://discuss.elastic.co/t/unassigned-node-and-shards/19332/2 "2014-08-18T21:56:58Z")

</div>

First, 2 nodes is not a good number for distributed systems, so you must  
take extra care that you write to the index with write consistency "full".  
Otherwise, your system will be easily exposed to receive split brains, you  
get all kind of difficulties, missing documents etc.

Second, check your log files for disconnects and out of memory or other  
exceptions. This might give you enough hints about the resources you have  
allocated to ES so you can fix the problem.

Third, it would be helpful if you describe your configuration how you index  
and what versions you use.

Jörg

On Mon, Aug 18, 2014 at 10:29 PM, IronMan2014 [sabdalla80@gmail.com](mailto:sabdalla80@gmail.com) wrote:

> I saw this problem twice now.  
> I start with a Green two-node cluster, default 5 shards/node, I index  
> about 50,000 docs, shards/replicas look great and well balanced across the  
> 2 nodes.
> 
> I try the same test with 8 million docs. I come back when its done, and I  
> see all primary shards on node1 and 2 replicas on node2 and three  
> unassigned replicas on a third "unassigned" node.
> 
> I will look through the logs, but I was wondering if anyone has seen  
> something similar or has any idea where/why this is coming from before I  
> dig?
> 
> --  
> 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/2bddca5e-ea3d-4804-9a0d-47d98bab96c1%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2bddca5e-ea3d-4804-9a0d-47d98bab96c1%40googlegroups.com)  
> [https://groups.google.com/d/msgid/elasticsearch/2bddca5e-ea3d-4804-9a0d-47d98bab96c1%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/2bddca5e-ea3d-4804-9a0d-47d98bab96c1%40googlegroups.com?utm_medium=email&utm_source=footer)  
> .  
> For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/CAKdsXoHc\_f-0hoO%3DgKwrBocBrDJxtxiwWvAKc%2B5O11SYuNxrbw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHc_f-0hoO%3DgKwrBocBrDJxtxiwWvAKc%2B5O11SYuNxrbw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![IronMike](https://avatars.discourse-cdn.com/v4/letter/i/e9a140/32.png) [@IronMike](https://discuss.elastic.co/u/IronMike)\
**Post date:** [August 19, 2014, 1:37pm UTC](https://discuss.elastic.co/t/unassigned-node-and-shards/19332/3 "2014-08-19T13:37:26Z")

</div>

Thanks. I do realize that I need more nodes, but it was only meant for  
testing.  
Q1) Can you expand a bit on 'full' writes, I am not sure what you meant by  
it (reference also would help.

As far as the setup, its the normal 2 node EC2 cluster, Java transport  
Client with Bulk processor.  
Q2) My 2 ymls have the default setup for the most part, do I need to tell  
one to be a master and the other not? (By default both nodes will be  
eligible to be master candidates). As far as the split brain, I thought its  
recommended to be 2?N +1, so for 2 nodes, it would be 2.

On Monday, August 18, 2014 5:57:08 PM UTC-4, Jörg Prante wrote:

> First, 2 nodes is not a good number for distributed systems, so you must  
> take extra care that you write to the index with write consistency "full".  
> Otherwise, your system will be easily exposed to receive split brains, you  
> get all kind of difficulties, missing documents etc.
> 
> Second, check your log files for disconnects and out of memory or other  
> exceptions. This might give you enough hints about the resources you have  
> allocated to ES so you can fix the problem.
> 
> Third, it would be helpful if you describe your configuration how you  
> index and what versions you use.
> 
> Jörg
> 
> On Mon, Aug 18, 2014 at 10:29 PM, IronMan2014 \<[sabda...@gmail.com](mailto:sabda...@gmail.com)  
> \<javascript:\>\> wrote:
> 
> > I saw this problem twice now.  
> > I start with a Green two-node cluster, default 5 shards/node, I index  
> > about 50,000 docs, shards/replicas look great and well balanced across the  
> > 2 nodes.
> > 
> > I try the same test with 8 million docs. I come back when its done, and I  
> > see all primary shards on node1 and 2 replicas on node2 and three  
> > unassigned replicas on a third "unassigned" node.
> > 
> > I will look through the logs, but I was wondering if anyone has seen  
> > something similar or has any idea where/why this is coming from before I  
> > dig?
> > 
> > --  
> > 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 [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > To view this discussion on the web visit  
> > [https://groups.google.com/d/msgid/elasticsearch/2bddca5e-ea3d-4804-9a0d-47d98bab96c1%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/2bddca5e-ea3d-4804-9a0d-47d98bab96c1%40googlegroups.com)  
> > [https://groups.google.com/d/msgid/elasticsearch/2bddca5e-ea3d-4804-9a0d-47d98bab96c1%40googlegroups.com?utm\_medium=email&utm\_source=footer](https://groups.google.com/d/msgid/elasticsearch/2bddca5e-ea3d-4804-9a0d-47d98bab96c1%40googlegroups.com?utm_medium=email&utm_source=footer)  
> > .  
> > For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

--  
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/32658796-0975-4adf-ac5c-e2f6dd023051%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/32658796-0975-4adf-ac5c-e2f6dd023051%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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, 1:07am UTC](https://discuss.elastic.co/t/unassigned-node-and-shards/19332/4 "2017-07-06T01:07:43Z")

</div>

Closed on July 6, 2017, 1:07am UTC


