# Adding a new node: how to prime the data
**URL:** https://discuss.elastic.co/t/adding-a-new-node-how-to-prime-the-data/20855
**Category:** Elasticsearch
**Created:** [November 20, 2014, 5:48am UTC](https://discuss.elastic.co/t/adding-a-new-node-how-to-prime-the-data/20855 "2014-11-20T05:48:36Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@Yves\_Dorfsman](https://discuss.elastic.co/u/Yves_Dorfsman)
#### Post date: [November 20, 2014, 5:48am UTC](https://discuss.elastic.co/t/adding-a-new-node-how-to-prime-the-data/20855/1 "2014-11-20T05:48:36Z")
We upgrade our clusters by adding new nodes, increase the number or
replicas on the indices, let the new node catch up, then exclude the old
node, and reduce the number of replicas on the indices.
One cluster has a large index for which this operation takes hours. We
tried to copy data from an existing node, but it copies everything
regardless (I suspect it has no way to know what's new or not?). We're do
plan to split that index into smaller shards, but in the meantime we are
wondering if there is a better way of doing this?
Thanks.
* * *
[http://yves.zioup.com](http://yves.zioup.com)
gpg: 4096R/32B0F416
--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/60428bf4-675b-47bd-8b8b-e90e7e967b0b%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/60428bf4-675b-47bd-8b8b-e90e7e967b0b%40googlegroups.com).
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 6, 2017, 12:48am UTC](https://discuss.elastic.co/t/adding-a-new-node-how-to-prime-the-data/20855/2 "2017-07-06T00:48:50Z")