# Elasticsearch query result consensus across replica nodes

**URL:** <https://discuss.elastic.co/t/elasticsearch-query-result-consensus-across-replica-nodes/94472>\
**Category:** Elasticsearch\
**Created:** [July 25, 2017, 11:58am UTC](https://discuss.elastic.co/t/elasticsearch-query-result-consensus-across-replica-nodes/94472 "2017-07-25T11:58:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![NathanBaulch](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nathanbaulch/32/19785_2.png) [@NathanBaulch](https://discuss.elastic.co/u/NathanBaulch)\
**Post date:** [July 25, 2017, 11:58am UTC](https://discuss.elastic.co/t/elasticsearch-query-result-consensus-across-replica-nodes/94472/1 "2017-07-25T11:58:03Z")

</div>

I'm working on a project that uses Elasticsearch as a primary data store for sensitive data that needs to be resilient to corruption. The indexes are split into 5 shards with 2 replicas across 3 machines.

Is there a built in way to send queries to all 3 nodes and check for consensus? Is this something I need to code explicitly in my client or can the data node I happen to connect to handle this for me?

Also, does Elasticsearch perform any parity/integrity checks on source and index data, aside from the potentially slow startup check when `index.shard.check_on_startup` is enabled? Or does this need to be handled by a fault tolerant FS or in hardware with RAID-5/10?

---

<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:** [July 26, 2017, 8:20pm UTC](https://discuss.elastic.co/t/elasticsearch-query-result-consensus-across-replica-nodes/94472/2 "2017-07-26T20:20:43Z")

</div>

> [@NathanBaulch](#):
>
> Is this something I need to code explicitly in my client or can the data node I happen to connect to handle this for me?

The former.

> [@NathanBaulch](#):
>
> Also, does Elasticsearch perform any parity/integrity checks on source and index data

We did add checksums to the entire stack (lucene and Elasticsearch) a while back.

---

<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:** [August 23, 2017, 8:21pm UTC](https://discuss.elastic.co/t/elasticsearch-query-result-consensus-across-replica-nodes/94472/3 "2017-08-23T20:21:00Z")

</div>

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