# Elasticsearch data node - read & write affect performance

**URL:** <https://discuss.elastic.co/t/elasticsearch-data-node-read-write-affect-performance/117287>\
**Category:** Elasticsearch\
**Created:** [January 27, 2018, 6:26am UTC](https://discuss.elastic.co/t/elasticsearch-data-node-read-write-affect-performance/117287 "2018-01-27T06:26:11Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hitesh\_Baldaniya](https://avatars.discourse-cdn.com/v4/letter/h/439d5e/32.png) [@Hitesh\_Baldaniya](https://discuss.elastic.co/u/Hitesh_Baldaniya)\
**Post date:** [January 27, 2018, 6:26am UTC](https://discuss.elastic.co/t/elasticsearch-data-node-read-write-affect-performance/117287/1 "2018-01-27T06:26:11Z")

</div>

As per documentation, we can have separate data node by making configuration.

When i actually did this configuration on my cluster i experienced following.

My read and write at same moment are affected, when ever I am updating content in ES read is getting affected by write.

How can i over come such a issue while scaling elasticsearch for larger extent of data?

---

<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 24, 2018, 6:26am UTC](https://discuss.elastic.co/t/elasticsearch-data-node-read-write-affect-performance/117287/2 "2018-02-24T06:26:47Z")

</div>

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