We are trying to replicate the data on one ElasticSearch cluster onto
another using rsync and so far, to no avail. We'd like to perform some
recovery experiments using v.0.90.0.RC1 but we need to assume the data and
setup of one environment (Cluster A) to our testing environment (Cluster
B). We have the following questions:
Is there a specific place the cluster identity is coded within
ElasticSearch, if anywhere?
Is it possible to make Cluster A assume the data of Cluster B,
clobbering Cluster B's original contents?
Is it possible to replicate an index from Cluster A to Cluster B and
force it to assume the shards, etc?
This is purely for developmental purposes, so it doesn't matter if we need
to restart ElasitcSearch or if we need to manually modify any files. We are using
a local gateway.
This should be easy - just rsync over the data/ directory. The only thing
that you may need to change is the cluster name, which forms part of the
path under data/
We are trying to replicate the data on one Elasticsearch cluster onto
another using rsync and so far, to no avail. We'd like to perform some
recovery experiments using v.0.90.0.RC1 but we need to assume the data and
setup of one environment (Cluster A) to our testing environment (Cluster
B). We have the following questions:
Is there a specific place the cluster identity is coded within
Elasticsearch, if anywhere?
Is it possible to make Cluster A assume the data of Cluster B,
clobbering Cluster B's original contents?
Is it possible to replicate an index from Cluster A to Cluster B and
force it to assume the shards, etc?
This is purely for developmental purposes, so it doesn't matter if we need
to restart ElasitcSearch or if we need to manually modify any files. We
are using a local gateway.
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.