# Unique search for BiDirectional CCR

**URL:** <https://discuss.elastic.co/t/unique-search-for-bidirectional-ccr/234238>\
**Category:** Elasticsearch\
**Tags:** ccr-cross-cluster-replication\
**Created:** [May 26, 2020, 4:06am UTC](https://discuss.elastic.co/t/unique-search-for-bidirectional-ccr/234238 "2020-05-26T04:06:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![vikram1](https://avatars.discourse-cdn.com/v4/letter/v/9f8e36/32.png) [@vikram1](https://discuss.elastic.co/u/vikram1)\
**Post date:** [May 26, 2020, 4:06am UTC](https://discuss.elastic.co/t/unique-search-for-bidirectional-ccr/234238/1 "2020-05-26T04:06:00Z")

</div>

Hello, I have setup CCR between 2 clusters, and based on the blog from elastic I have set it up. Below is the link,

> **[Bi-directional replication with Elasticsearch cross-cluster replication (CCR)](https://www.elastic.co/blog/bi-directional-replication-with-elasticsearch-cross-cluster-replication-ccr)**
>
> Learn how to use Elasticsearch cross-cluster replication (CCR) and bi-directional replication to create a multi-datacenter replication architecture to automatically withstand a DC failure.

However, when I search either cluster using alias, I'm getting duplicate (same record from both leader and follower in the cluster). Also, if there are any updates to one of the document, I needed to reindex the document from follower to leader.

Is there any best approach/architectural pattern available that I can leverage?

thanks,  
Vik

---

<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:** [June 23, 2020, 4:06am UTC](https://discuss.elastic.co/t/unique-search-for-bidirectional-ccr/234238/2 "2020-06-23T04:06:07Z")

</div>

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