# Replicate whole data to a specific node

**URL:** <https://discuss.elastic.co/t/replicate-whole-data-to-a-specific-node/152476>\
**Category:** Elasticsearch\
**Created:** [October 15, 2018, 10:57am UTC](https://discuss.elastic.co/t/replicate-whole-data-to-a-specific-node/152476 "2018-10-15T10:57:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mosmanmix](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mosmanmix/32/36519_2.png) [@mosmanmix](https://discuss.elastic.co/u/mosmanmix)\
**Post date:** [October 15, 2018, 10:57am UTC](https://discuss.elastic.co/t/replicate-whole-data-to-a-specific-node/152476/1 "2018-10-15T10:57:42Z")

</div>

Hi,

we have a production cluster based on 4 data nodes used by our frontend application.

We have recently developed a feature that consumes a lot of resource from this cluster, and when one is using this feature, the other users are impacted with low performance (due to lack of space within the search pool).

So I wonder how to handle without to have two separate clusters (one for this feature and another for the rest of the application) ?

Is there a way to create a dedicated node with all the shards replicated, and to route the requests to this node ?

By the way we are using a quite old ES version (2.0)

Thank you in advance,  
Metin

---

<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:** [November 12, 2018, 10:57am UTC](https://discuss.elastic.co/t/replicate-whole-data-to-a-specific-node/152476/2 "2018-11-12T10:57:43Z")

</div>

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