# Separating nodes purely for bulk indexing

**URL:** https://discuss.elastic.co/t/separating-nodes-purely-for-bulk-indexing/58838
**Category:** Elasticsearch
**Created:** [August 24, 2016, 3:13pm UTC](https://discuss.elastic.co/t/separating-nodes-purely-for-bulk-indexing/58838 "2016-08-24T15:13:13Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![jaydanielian](https://avatars.discourse-cdn.com/v4/letter/j/85e7bf/32.png) [@jaydanielian](https://discuss.elastic.co/u/jaydanielian)
#### Post date: [August 24, 2016, 3:13pm UTC](https://discuss.elastic.co/t/separating-nodes-purely-for-bulk-indexing/58838/1 "2016-08-24T15:13:13Z")

</div>

We have a four node cluster (with two master nodes and two data nodes). Our indexes are basically read only after we bulk index the data (which occurs monthly). While indexing our new data, we really push the CPU and IO of the servers - during this time the search performance degrades.

My question is - is it possible to stand up new temporary servers just to handle the index creation? Then once its created replicate the index to the other nodes? Or is it possible to only use two servers to handle the indexing requests, and tell our clients to only route search/get requests to the other servers? Basically I want to find out the easiest way we can isolate searching traffic and indexing traffic within our cluster. I am not opposed to standing up dedicated temporary indexing nodes if need be , but if we could just split the traffic amongst the existing four servers - that might be simpler.

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: [August 26, 2016, 9:37am UTC](https://discuss.elastic.co/t/separating-nodes-purely-for-bulk-indexing/58838/2 "2016-08-26T09:37:49Z")

</div>

> [@jaydanielian](#):
>
> My question is - is it possible to stand up new temporary servers just to handle the index creation?

Yes. Basically you do this [“Hot-Warm” architecture | Elastic Blog](https://www.elastic.co/blog/hot-warm-architecture)

> [@jaydanielian](#):
>
> Or is it possible to only use two servers to handle the indexing requests, and tell our clients to only route search/get requests to the other servers?

Possibly, but it's messy. You are better off doing ^

---

<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 5, 2017, 10:24pm UTC](https://discuss.elastic.co/t/separating-nodes-purely-for-bulk-indexing/58838/3 "2017-07-05T22:24:59Z")

</div>


