# Move a one node index to a different machine

**URL:** <https://discuss.elastic.co/t/move-a-one-node-index-to-a-different-machine/10985>\
**Category:** Elasticsearch\
**Created:** [March 4, 2013, 5:28am UTC](https://discuss.elastic.co/t/move-a-one-node-index-to-a-different-machine/10985 "2013-03-04T05:28:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Josh\_Cutler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/josh_cutler/32/2462_2.png) [@Josh\_Cutler](https://discuss.elastic.co/u/Josh_Cutler)\
**Post date:** [March 4, 2013, 5:28am UTC](https://discuss.elastic.co/t/move-a-one-node-index-to-a-different-machine/10985/1 "2013-03-04T05:28:33Z")

</div>

I currently have a one node ES index that resides on a machine at  
engineyard. I want to move this index elsewhere but the indexing task  
could take upward of 24 hours so I was hoping that I could just move the  
files in the index to a different node. I have read previous threads on  
this topic that were complicated by that fact that the index was  
distributed. In my case it is just one location on an EBS drive. Just  
moving the files seems to break the ES index as it just shuffled records  
around when I started ES up (I think I missed some metadata). Is there a  
better way to do this?

Thanks,  
-=Josh

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\
**Post date:** [March 4, 2013, 9:16am UTC](https://discuss.elastic.co/t/move-a-one-node-index-to-a-different-machine/10985/2 "2013-03-04T09:16:44Z")

</div>

Hey Josh,

did you flush before moving the index?  
([Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-flush.html))  
I am wondering if you are indexing into that node while you are doing this.  
You should be able to just copy your entire data directory etc. from one  
machine to another though.

The other possibility would be to start up another node on the target  
machine and then exclude the index from the machine it's on right now see

> **[Elasticsearch Platform — Find real-time answers at scale](https://www.elastic.co)**
>
> Power insights and outcomes with the Elasticsearch Platform and AI. See into your data and find answers that matter with enterprise solutions designed to help you build, observe, and protect. Try Elasticsearch free today.

and look for "\_ip"

hope that helps?

simon

On Monday, March 4, 2013 6:28:33 AM UTC+1, Josh Cutler wrote:

> I currently have a one node ES index that resides on a machine at  
> engineyard. I want to move this index elsewhere but the indexing task  
> could take upward of 24 hours so I was hoping that I could just move the  
> files in the index to a different node. I have read previous threads on  
> this topic that were complicated by that fact that the index was  
> distributed. In my case it is just one location on an EBS drive. Just  
> moving the files seems to break the ES index as it just shuffled records  
> around when I started ES up (I think I missed some metadata). Is there a  
> better way to do this?
> 
> Thanks,  
> -=Josh

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Josh\_Cutler](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/josh_cutler/32/2462_2.png) [@Josh\_Cutler](https://discuss.elastic.co/u/Josh_Cutler)\
**Post date:** [March 4, 2013, 6:41pm UTC](https://discuss.elastic.co/t/move-a-one-node-index-to-a-different-machine/10985/3 "2013-03-04T18:41:34Z")

</div>

Thank you, I did not flush the indices. I'll give that a try and I'm  
betting it will fix my problem.

Cheers,  
-=Josh

On Mon, Mar 4, 2013 at 4:16 AM, simonw [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com)wrote:

> Hey Josh,
> 
> did you flush before moving the index? (  
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/api/admin-indices-flush.html))  
> I am wondering if you are indexing into that node while you are doing this.  
> You should be able to just copy your entire data directory etc. from one  
> machine to another though.
> 
> The other possibility would be to start up another node on the target  
> machine and then exclude the index from the machine it's on right now see
> 
> [Elasticsearch Platform — Find real-time answers at scale | Elastic](http://www.elasticsearch.org/guide/reference/index-modules/allocation.html)
> 
> and look for "\_ip"
> 
> hope that helps?
> 
> simon
> 
> On Monday, March 4, 2013 6:28:33 AM UTC+1, Josh Cutler wrote:
> 
> > I currently have a one node ES index that resides on a machine at  
> > engineyard. I want to move this index elsewhere but the indexing task  
> > could take upward of 24 hours so I was hoping that I could just move the  
> > files in the index to a different node. I have read previous threads on  
> > this topic that were complicated by that fact that the index was  
> > distributed. In my case it is just one location on an EBS drive. Just  
> > moving the files seems to break the ES index as it just shuffled records  
> > around when I started ES up (I think I missed some metadata). Is there a  
> > better way to do this?
> > 
> > Thanks,  
> > -=Josh
> 
> --  
> You received this message because you are subscribed to a topic in the  
> Google Groups "elasticsearch" group.  
> To unsubscribe from this topic, visit  
> [https://groups.google.com/d/topic/elasticsearch/EX8xmdxLY\_c/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/EX8xmdxLY_c/unsubscribe?hl=en-US)  
> .  
> To unsubscribe from this group and all its topics, send an email to  
> [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
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).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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 6, 2017, 2:48am UTC](https://discuss.elastic.co/t/move-a-one-node-index-to-a-different-machine/10985/4 "2017-07-06T02:48:30Z")

</div>


