Also try this tool for more easily aggregating FS repo snapshots across a
cluster for restoring on a different cluster. I had to make this tool for a
similar scenario I had, might help in your situation
too https://github.com/bitsofinfo/elasticsearch-snapshot-manager
On Thursday, May 14, 2015
You're better off using the snapshot and restore functionality than doing
your method.
I'm not sure what you are trying to do though
On 15 May 2015 at 09:49, Frederico Ferreira frederic...@gmail.com wrote:
I'm sorry for the long delay it took to answer.
Every index is a folder inside the data
I'm sorry for the long delay it took to answer.
Every index is a folder inside the data folder. I just simply compressed
those folders and sent to S3.
But, now, we just found an answer:
- we built (at another dc) another ES cluster and we've put those
folders inside the data directory
-
This is my first e-mail, so, if this problem is already explained, i'm
sorry, couldn't find out where it is.
I'm out of ideas. This is my question:
I had an Elasticsearch up and running with 1 replica, 5 shards, 1 master
(data false) and 10 slaves, and every index configured by day (from
