# Query on Elasticsearch storage

**URL:** <https://discuss.elastic.co/t/query-on-elasticsearch-storage/116612>\
**Category:** Elasticsearch\
**Created:** [January 23, 2018, 8:03am UTC](https://discuss.elastic.co/t/query-on-elasticsearch-storage/116612 "2018-01-23T08:03:43Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![rrs](https://avatars.discourse-cdn.com/v4/letter/r/d9b06d/32.png) [@rrs](https://discuss.elastic.co/u/rrs)\
**Post date:** [January 23, 2018, 8:03am UTC](https://discuss.elastic.co/t/query-on-elasticsearch-storage/116612/1 "2018-01-23T08:03:43Z")

</div>

Hi All,  
We have a 3node elasticsearch cluster with both master/data running fine now. Each node has 1TB SAN storage and occupied 2.5TB data and indexes are being created with 5 primary shards and 1 replica distributing among 3 nodes.

My query is what happens, if 1node is failed? Does Elasticsearch promote any replica as primary and adjusts data of node1 on two nodes? In that case my two nodes wouldn't accommodate 800GB. Or, data on node1 will be ignored and new indexes will be created on available two nodes with same 5 primary and 1 replica each?

Please correct me, if am wrong.

---

<div class="post-metadata">

**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\
**Post date:** [January 23, 2018, 6:09pm UTC](https://discuss.elastic.co/t/query-on-elasticsearch-storage/116612/2 "2018-01-23T18:09:35Z")

</div>

> Does Elasticsearch promote any replica as primary

Yes.

> adjusts data of node1 on two nodes? In that case my two nodes wouldn't accommodate 800GB.

If disk usage is above the low disk watermark ([Disk-based shard allocation | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/disk-allocator.html)), Elasticsearch will not create a replica in order to not make the node run out of space. As a result of this your cluster will likely be in a yellow state since not all shards would be allocated.

---

<div class="post-metadata">

**Author:** ![rrs](https://avatars.discourse-cdn.com/v4/letter/r/d9b06d/32.png) [@rrs](https://discuss.elastic.co/u/rrs)\
**Post date:** [January 23, 2018, 8:35pm UTC](https://discuss.elastic.co/t/query-on-elasticsearch-storage/116612/3 "2018-01-23T20:35:58Z")

</div>

Hi Adrien,

Thank you for update. If node1 is down, how other nodes communicate with failed node to transfer data? And, if Elasticsearch promotes replicas as primary, what is the essential to transfer data from failed node since the data available on remaining nodes?

---

<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:** [February 20, 2018, 8:36pm UTC](https://discuss.elastic.co/t/query-on-elasticsearch-storage/116612/4 "2018-02-20T20:36:14Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![jpountz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jpountz/32/45836_2.png) [@jpountz](https://discuss.elastic.co/u/jpountz)\
**Post date:** [March 29, 2018, 5:21pm UTC](https://discuss.elastic.co/t/query-on-elasticsearch-storage/116612/5 "2018-03-29T17:21:18Z")

</div>

> [@rrs](#):
>
> If node1 is down, how other nodes communicate with failed node to transfer data?

It doesn't but you would typically have the data on some other node.

> [@rrs](#):
>
> And, if Elasticsearch promotes replicas as primary, what is the essential to transfer data from failed node since the data available on remaining nodes?

It would transfer the data from this new primary to a new node so that the number of replicas is still honored.