# Remote cluster between es and opensearch

**URL:** <https://forum.opensearch.org/t/remote-cluster-between-es-and-opensearch/13743>\
**Category:** OpenSearch\
**Tags:** troubleshoot\
**Created:** [April 2, 2023, 1:15pm UTC](https://forum.opensearch.org/t/remote-cluster-between-es-and-opensearch/13743 "2023-04-02T13:15:51Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![taltsafrir](https://avatars.discourse-cdn.com/v4/letter/t/a698b9/32.png) [@taltsafrir](https://forum.opensearch.org/u/taltsafrir)\
**Post date:** [April 2, 2023, 1:15pm UTC](https://forum.opensearch.org/t/remote-cluster-between-es-and-opensearch/13743/1 "2023-04-02T13:15:51Z")

</div>

hi, im trying to connect between elasticsearch (7.10.2 and without certs) to opensearch (with configured certs)  
is that possible?

---

<div class="post-metadata">

**Author:** ![dtaivpp](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/dtaivpp/32/2814_2.png) [@dtaivpp](https://forum.opensearch.org/u/dtaivpp)\
**Post date:** [April 3, 2023, 1:22pm UTC](https://forum.opensearch.org/t/remote-cluster-between-es-and-opensearch/13743/2 "2023-04-03T13:22:40Z")

</div>

When you say connect you mean upgrade or do something along the lines of cross cluster replication?

---

<div class="post-metadata">

**Author:** ![taltsafrir](https://avatars.discourse-cdn.com/v4/letter/t/a698b9/32.png) [@taltsafrir](https://forum.opensearch.org/u/taltsafrir)\
**Post date:** [April 3, 2023, 1:26pm UTC](https://forum.opensearch.org/t/remote-cluster-between-es-and-opensearch/13743/3 "2023-04-03T13:26:48Z")

</div>

I meant cross cluster replication  
I tried to configure opensearch as the remote but when I try to reindex the error is: empty replay

---

<div class="post-metadata">

**Author:** ![dtaivpp](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/dtaivpp/32/2814_2.png) [@dtaivpp](https://forum.opensearch.org/u/dtaivpp)\
**Post date:** [April 3, 2023, 5:47pm UTC](https://forum.opensearch.org/t/remote-cluster-between-es-and-opensearch/13743/4 "2023-04-03T17:47:40Z")

</div>

Hey what version of OpenSearch are you using? I think this may need to be between 7.10.x and 1.3.x.

Also, why are you doing this? Just curious as there might be another way.

---

<div class="post-metadata">

**Author:** ![taltsafrir](https://avatars.discourse-cdn.com/v4/letter/t/a698b9/32.png) [@taltsafrir](https://forum.opensearch.org/u/taltsafrir)\
**Post date:** [April 4, 2023, 7:31am UTC](https://forum.opensearch.org/t/remote-cluster-between-es-and-opensearch/13743/5 "2023-04-04T07:31:56Z")

</div>

hey 🙂  
so we are migrating from elastic 7.10.2 to opensearch 2.5.0 and we need to have a remote cluster for our users  
about the reindex- the purpose is to move all visualisations from elastic to opensearch so we need to reindex the .kibana index

---

<div class="post-metadata">

**Author:** ![dtaivpp](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/dtaivpp/32/2814_2.png) [@dtaivpp](https://forum.opensearch.org/u/dtaivpp)\
**Post date:** [April 4, 2023, 5:32pm UTC](https://forum.opensearch.org/t/remote-cluster-between-es-and-opensearch/13743/6 "2023-04-04T17:32:36Z")

</div>

Ah I see, so unfortunately CCR will not work in that way. It is always setup to go from a lower to higher version so it will likely see that Elasticsearch is 7.10 and will only allow to transfer from OpenSearch to Elasticsearch.

Have you tried a [rolling upgrade](https://opensearch.org/docs/latest/install-and-configure/upgrade-opensearch/rolling-upgrade/)? This should attempt to preserve your dashboards and data. With this option you could go from 7.10 → 1.3.x → 2.x.x. You would need to do it in that order though as each major release has breaking changes.

---

<div class="post-metadata">

**Author:** ![amitai](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/amitai/32/1072_2.png) [@amitai](https://forum.opensearch.org/u/amitai)\
**Post date:** [April 4, 2023, 6:27pm UTC](https://forum.opensearch.org/t/remote-cluster-between-es-and-opensearch/13743/7 "2023-04-04T18:27:29Z")

</div>

Maybe take a snapshot to s3 and restore to the opensearch cluster?

---

<div class="post-metadata">

**Author:** ![taltsafrir](https://avatars.discourse-cdn.com/v4/letter/t/a698b9/32.png) [@taltsafrir](https://forum.opensearch.org/u/taltsafrir)\
**Post date:** [April 4, 2023, 6:35pm UTC](https://forum.opensearch.org/t/remote-cluster-between-es-and-opensearch/13743/8 "2023-04-04T18:35:03Z")

</div>

yes, I tried but it didn’t work

---

<div class="post-metadata">

**Author:** ![dtaivpp](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/dtaivpp/32/2814_2.png) [@dtaivpp](https://forum.opensearch.org/u/dtaivpp)\
**Post date:** [April 4, 2023, 6:40pm UTC](https://forum.opensearch.org/t/remote-cluster-between-es-and-opensearch/13743/9 "2023-04-04T18:40:32Z")

</div>

Which didnt work s3 or rolling upgrade? and did it give an error?

---

<div class="post-metadata">

**Author:** ![amitai](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/amitai/32/1072_2.png) [@amitai](https://forum.opensearch.org/u/amitai)\
**Post date:** [April 4, 2023, 6:41pm UTC](https://forum.opensearch.org/t/remote-cluster-between-es-and-opensearch/13743/10 "2023-04-04T18:41:31Z")

</div>

Ok if going via s3 didnt work - seems like going through opensearch 1.x is a requirement.  
If you are adventurous you can create a single node cluster with opensearch 1.3.  
Reindex to it. Then reindex to the opensearch 2.5 cluster.

---

<div class="post-metadata">

**Author:** ![radu.gheorghe](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/radu.gheorghe/32/3516_2.png) [@radu.gheorghe](https://forum.opensearch.org/u/radu.gheorghe)\
**Post date:** [April 6, 2023, 8:20am UTC](https://forum.opensearch.org/t/remote-cluster-between-es-and-opensearch/13743/11 "2023-04-06T08:20:33Z")

</div>

You can also use something external like Logstash to connect to both clusters and do the reindexing. Here’s a recipe: [Recipe: Reindexing Elasticsearch Documents with Logstash - Sematext](https://sematext.com/blog/recipe-reindexing-elasticsearch-documents-with-logstash/)
