Thank you for letting me know. May I know what are all the options available to do the CCR in open source version. Can you share your thoughts on this.
There is no way to do that within Elasticsearch with the free basic license. Before CCR was created a reasonably common way to achieve this was to feed the two clusters in parallel, e.g. by having two Logstash instances feed the clusters from Kafka or some other message queue, but whether this is appropriate or not depends on your use case.
Thank you for the response. If it is Active/Active then may I know what are the best ways to achieve CCR apart from feeding the two clusters in parallel?
Please share your thoughts on this? Is it possible to update the records on follower index after replication? We are looking for Active/Active model. So inserts, updates and deletes on the index will happen on both the clusters. So we are looking for Bi-directional approach.
CCR does as far as I know not support active-active replication. Please see this blog post for details. I am not aware of any solution to achieve this in Elasticsearch.
Ok. But we have a question on Active/Passive model as well.
Cluster 1 we are creating indexes and performing all write operations. Then replication will happen automatically on the other cluster (Cluster 2).
If we have major outage on Cluster1 then only Cluster 2 will be available for the operation. As you said Read will work fine, since follower indexes are read only. But what we can do for write here.
How will we achieve DR (Disaster Recovery) process?
I believe you would need to terminate replication in order to transform it into a leader index that you can make updates to and then follow once the other site comes back up.
Yes. Replication has been paused by doing select the follower index and pause replication (On cluster 2). When the follower index status changes to Paused, reselect the follower index and choose to unfollow the leader index. Then the index started acting like a normal index to perform insert, update and delete operations. Below is my question.
After some point cluster 1 recovered from crash.. Then how the updates or inserts or deletes happened on cluster 2 index will navigate to Cluster 1? Because Cluster 1 already have an index with the same name with old data. How to achieve this?
This is normal Disaster Recovery process. It helps if you share how we can achieve this and it may help us to make the decision to go with Enterprise edition.
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.