# 2 Cluster Elasticsearch

**URL:** <https://discuss.elastic.co/t/2-cluster-elasticsearch/96894>\
**Category:** Elasticsearch\
**Created:** [August 14, 2017, 2:26am UTC](https://discuss.elastic.co/t/2-cluster-elasticsearch/96894 "2017-08-14T02:26:13Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![jogoinar10](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jogoinar10/32/20068_2.png) [@jogoinar10](https://discuss.elastic.co/u/jogoinar10)\
**Post date:** [August 14, 2017, 2:26am UTC](https://discuss.elastic.co/t/2-cluster-elasticsearch/96894/1 "2017-08-14T02:26:14Z")

</div>

Can I setup 2 cluster with 1 node and sync data?  
My purpose is that, if ever 1 cluster i down, there's a failover on another system.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 14, 2017, 3:06am UTC](https://discuss.elastic.co/t/2-cluster-elasticsearch/96894/2 "2017-08-14T03:06:06Z")

</div>

There is currently nothing that will natively do this. There are changes coming to 6.0 that will eventually allow it though.

For now you need to use methods like these - [https://www.elastic.co/blog/clustering\_across\_multiple\_data\_centers](https://www.elastic.co/blog/clustering_across_multiple_data_centers)

---

<div class="post-metadata">

**Author:** ![jogoinar10](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jogoinar10/32/20068_2.png) [@jogoinar10](https://discuss.elastic.co/u/jogoinar10)\
**Post date:** [August 14, 2017, 3:43am UTC](https://discuss.elastic.co/t/2-cluster-elasticsearch/96894/3 "2017-08-14T03:43:18Z")

</div>

Thank you for your response @warkolm

Can you please help me understand the option 1?

> Real-time Availability Across Geographic Regions

Does this means that i will index my data per cluster by using code? and logstash?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 14, 2017, 4:09am UTC](https://discuss.elastic.co/t/2-cluster-elasticsearch/96894/4 "2017-08-14T04:09:24Z")

</div>

Yes that is one option.

---

<div class="post-metadata">

**Author:** ![jogoinar10](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jogoinar10/32/20068_2.png) [@jogoinar10](https://discuss.elastic.co/u/jogoinar10)\
**Post date:** [August 14, 2017, 8:19am UTC](https://discuss.elastic.co/t/2-cluster-elasticsearch/96894/5 "2017-08-14T08:19:23Z")

</div>

It could transfer the index automatically (sync) between the cluster?

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 14, 2017, 8:39am UTC](https://discuss.elastic.co/t/2-cluster-elasticsearch/96894/6 "2017-08-14T08:39:26Z")

</div>

Not automatically, no.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 11, 2017, 8:39am UTC](https://discuss.elastic.co/t/2-cluster-elasticsearch/96894/7 "2017-09-11T08:39:29Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.