# ES freezes with number of replicas \> 1

**URL:** <https://discuss.elastic.co/t/es-freezes-with-number-of-replicas-1/5363>\
**Category:** Elasticsearch\
**Created:** [September 12, 2011, 10:05pm UTC](https://discuss.elastic.co/t/es-freezes-with-number-of-replicas-1/5363 "2011-09-12T22:05:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![mfeingold](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@mfeingold](https://discuss.elastic.co/u/mfeingold)\
**Post date:** [September 12, 2011, 10:05pm UTC](https://discuss.elastic.co/t/es-freezes-with-number-of-replicas-1/5363/1 "2011-09-12T22:05:27Z")

</div>

I was playing with different shard/replica settings on my indexes. In  
one of my experiments I set number of replicas to 2 and the request to  
index a document never returned. At the moment I have only one node  
set up, and I understand that 1 node and 2 replicas is not really a  
meaningful configuration, but freezing does not seem the right  
response here. What's interesting is that 1 replica with a single node

- still an invalid configuration works fine,

What am missing here?

---

<div class="post-metadata">

**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\
**Post date:** [September 12, 2011, 10:55pm UTC](https://discuss.elastic.co/t/es-freezes-with-number-of-replicas-1/5363/2 "2011-09-12T22:55:46Z")

</div>

It does not freeze, it will timeout after 1 minute (the default). When you  
index, by default, a quorum of shard/replica is expected to be allocated. in  
2 replica case, that quorum number is 2, and you only have 1 node, so only 1  
for each partition is allocated.

On Tue, Sep 13, 2011 at 1:05 AM, Michael Feingold [mfeingold@hill30.com](mailto:mfeingold@hill30.com)wrote:

> I was playing with different shard/replica settings on my indexes. In  
> one of my experiments I set number of replicas to 2 and the request to  
> index a document never returned. At the moment I have only one node  
> set up, and I understand that 1 node and 2 replicas is not really a  
> meaningful configuration, but freezing does not seem the right  
> response here. What's interesting is that 1 replica with a single node
> 
> - still an invalid configuration works fine,
> 
> What am missing here?

---

<div class="post-metadata">

**Author:** ![mfeingold](https://avatars.discourse-cdn.com/v4/letter/m/ecb155/32.png) [@mfeingold](https://discuss.elastic.co/u/mfeingold)\
**Post date:** [September 13, 2011, 9:37pm UTC](https://discuss.elastic.co/t/es-freezes-with-number-of-replicas-1/5363/3 "2011-09-13T21:37:17Z")

</div>

ah - makes sense

On Sep 12, 5:55 pm, Shay Banon [kim...@gmail.com](mailto:kim...@gmail.com) wrote:

> It does not freeze, it will timeout after 1 minute (the default). When you  
> index, by default, a quorum of shard/replica is expected to be allocated. in  
> 2 replica case, that quorum number is 2, and you only have 1 node, so only 1  
> for each partition is allocated.
> 
> On Tue, Sep 13, 2011 at 1:05 AM, Michael Feingold [mfeing...@hill30.com](mailto:mfeing...@hill30.com)wrote:
> 
> > I was playing with different shard/replica settings on my indexes. In  
> > one of my experiments I set number of replicas to 2 and the request to  
> > index a document never returned. At the moment I have only one node  
> > set up, and I understand that 1 node and 2 replicas is not really a  
> > meaningful configuration, but freezing does not seem the right  
> > response here. What's interesting is that 1 replica with a single node
> > 
> > - still an invalid configuration works fine,
> 
> > What am missing here?

---

<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, 3:54am UTC](https://discuss.elastic.co/t/es-freezes-with-number-of-replicas-1/5363/4 "2017-07-06T03:54:29Z")

</div>

Closed on July 6, 2017, 3:54am UTC


