I have the ES cluster with 9 shards and replicas, where all the data is
stored locally on the nodes. We have the process complete data migration
from one system to another. Since introduction of ES - we need to be able
to migrate also ES indices. We are using Netapp snap-mirror mechanism for
the rest of the data.
What would be the best practice, so, when the second system starts it will
actually build the cluster from migrated data.
I'm not sure I fully understand what you're trying to achieve. So you
want to migrate ES indices from one node to another, in case a node
goes down? Or from one cluster to another, or? Basically, I don't get
what you mean by "system".
I have the ES cluster with 9 shards and replicas, where all the data is
stored locally on the nodes. We have the process complete data migration
from one system to another. Since introduction of ES - we need to be able to
migrate also ES indices. We are using Netapp snap-mirror mechanism for the
rest of the data.
What would be the best practice, so, when the second system starts it will
actually build the cluster from migrated data.
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.