# How to transfer index from 1 node to a different node **URL:** \ **Category:** Elasticsearch\ **Created:** [January 4, 2019, 9:17am UTC](https://discuss.elastic.co/t/how-to-transfer-index-from-1-node-to-a-different-node/162917 "2019-01-04T09:17:50Z")\ **Posts on this page:** 7\ **Page:** 2
**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\ **Post date:** [January 8, 2019, 10:02am UTC](https://discuss.elastic.co/t/how-to-transfer-index-from-1-node-to-a-different-node/162917/21 "2019-01-08T10:02:31Z")
OK, then I really have no idea either. ---
**Author:** ![PolterFox](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/polterfox/32/29781_2.png) [@PolterFox](https://discuss.elastic.co/u/PolterFox)\ **Post date:** [January 8, 2019, 10:03am UTC](https://discuss.elastic.co/t/how-to-transfer-index-from-1-node-to-a-different-node/162917/22 "2019-01-08T10:03:37Z")
Is there any other option to get support to solve this problem. ---
**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\ **Post date:** [January 8, 2019, 2:00pm UTC](https://discuss.elastic.co/t/how-to-transfer-index-from-1-node-to-a-different-node/162917/23 "2019-01-08T14:00:20Z")
What is the version of both clusters? The remote seemed to be running 6.5.1, right? But what about the other one? ---
**Author:** ![PolterFox](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/polterfox/32/29781_2.png) [@PolterFox](https://discuss.elastic.co/u/PolterFox)\ **Post date:** [January 8, 2019, 2:13pm UTC](https://discuss.elastic.co/t/how-to-transfer-index-from-1-node-to-a-different-node/162917/24 "2019-01-08T14:13:34Z")
Both servers run version 6.5.1 ---
**Author:** ![PolterFox](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/polterfox/32/29781_2.png) [@PolterFox](https://discuss.elastic.co/u/PolterFox)\ **Post date:** [January 8, 2019, 2:31pm UTC](https://discuss.elastic.co/t/how-to-transfer-index-from-1-node-to-a-different-node/162917/25 "2019-01-08T14:31:10Z")
> [@PolterFox](#): > > "index": "myremoteindex-2018.12.\*" @Christian_Dahlqvist @dadoonet is there a problem using a wildcard in the index (from remote host) to get all indices of this month? ---
**Author:** ![dakrone](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dakrone/32/23351_2.png) [@dakrone](https://discuss.elastic.co/u/dakrone)\ **Post date:** [January 8, 2019, 2:49pm UTC](https://discuss.elastic.co/t/how-to-transfer-index-from-1-node-to-a-different-node/162917/26 "2019-01-08T14:49:25Z")
The exception you shared indicates that the remote server has rejected one or more search requests. It's possible that your cluster on the "read" side is overwhelmed by search requests currently, and when trying to re-index from it it rejects the queries the destination cluster is performing. Do you have ongoing queries being served by the remote cluster? Are they at a high volume? In regard to your previous question about wildcard indices, you can try re-indexing a single index at a time so that the query strain is not as high on the remote cluster side. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 5, 2019, 2:49pm UTC](https://discuss.elastic.co/t/how-to-transfer-index-from-1-node-to-a-different-node/162917/27 "2019-02-05T14:49:32Z")
Closed on February 5, 2019, 2:49pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed. [Previous page](https://discuss.elastic.co/t/how-to-transfer-index-from-1-node-to-a-different-node/162917.md?page=1)