# 0-all replicas and multiple es nodes per host never goes green

**URL:** <https://discuss.elastic.co/t/0-all-replicas-and-multiple-es-nodes-per-host-never-goes-green/184441>\
**Category:** Elasticsearch\
**Created:** [June 5, 2019, 6:41pm UTC](https://discuss.elastic.co/t/0-all-replicas-and-multiple-es-nodes-per-host-never-goes-green/184441 "2019-06-05T18:41:47Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andy\_Wick](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andy_wick/32/44017_2.png) [@Andy\_Wick](https://discuss.elastic.co/u/Andy_Wick)\
**Post date:** [June 5, 2019, 6:41pm UTC](https://discuss.elastic.co/t/0-all-replicas-and-multiple-es-nodes-per-host-never-goes-green/184441/1 "2019-06-05T18:41:47Z")

</div>

I'm playing with the terms lookup feature ([https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-terms-query.html#query-dsl-terms-lookup](https://www.elastic.co/guide/en/elasticsearch/reference/current/query-dsl-terms-query.html#query-dsl-terms-lookup)) which suggests my lookups index should be on all nodes.

If I

- have auto\_expand\_replicas set to 0-all
- run more then 1 node per host
- use a method that prevents the same shard on the same host (such as cluster.routing.allocation.same\_shard.host)

my cluster will now never go green and never have that lookups index on all nodes.  
[NO(the shard cannot be allocated on host address [10.10.10.10], where it already exists on node [XXXXXXXXXXXXXXXX]

Is there a work around so that this index breaks the rule and really is on all nodes? Since the indices that I will be searching against using this lookup are on all nodes, it would be great if lookups was too. Maybe I need a 0-allNodesReally feature?

Thanks!

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 5, 2019, 10:57pm UTC](https://discuss.elastic.co/t/0-all-replicas-and-multiple-es-nodes-per-host-never-goes-green/184441/2 "2019-06-05T22:57:17Z")

</div>

> [@Andy\_Wick](#):
>
> which suggests my lookups index should be on all nodes

Can you clarify where you are getting that from, I am not seeing the same thing when I read the doc.

---

<div class="post-metadata">

**Author:** ![Andy\_Wick](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andy_wick/32/44017_2.png) [@Andy\_Wick](https://discuss.elastic.co/u/Andy_Wick)\
**Post date:** [June 6, 2019, 12:34am UTC](https://discuss.elastic.co/t/0-all-replicas-and-multiple-es-nodes-per-host-never-goes-green/184441/3 "2019-06-06T00:34:10Z")

</div>

Am I reading this wrong?

> Also, consider using an index with a single shard and fully replicated across all nodes if the "reference" terms data is not large. The lookup terms filter will prefer to execute the get request on a local node if possible, reducing the need for networking.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [June 6, 2019, 12:35am UTC](https://discuss.elastic.co/t/0-all-replicas-and-multiple-es-nodes-per-host-never-goes-green/184441/4 "2019-06-06T00:35:21Z")

</div>

Ahh nope, that was my mistake.

---

<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 4, 2019, 12:35am UTC](https://discuss.elastic.co/t/0-all-replicas-and-multiple-es-nodes-per-host-never-goes-green/184441/5 "2019-07-04T00:35:26Z")

</div>

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