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?
did you flush before moving the index?
(Elasticsearch Platform — Find real-time answers at scale | Elastic)
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
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?
did you flush before moving the index? ( Elasticsearch Platform — Find real-time answers at scale | Elastic)
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
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?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.