# Leveraging CCR for A/B cluster setup

**URL:** <https://discuss.elastic.co/t/leveraging-ccr-for-a-b-cluster-setup/169081>\
**Category:** Elasticsearch\
**Created:** [February 19, 2019, 5:31pm UTC](https://discuss.elastic.co/t/leveraging-ccr-for-a-b-cluster-setup/169081 "2019-02-19T17:31:37Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![manoj\_faria](https://avatars.discourse-cdn.com/v4/letter/m/278dde/32.png) [@manoj\_faria](https://discuss.elastic.co/u/manoj_faria)\
**Post date:** [February 19, 2019, 5:31pm UTC](https://discuss.elastic.co/t/leveraging-ccr-for-a-b-cluster-setup/169081/1 "2019-02-19T17:31:37Z")

</div>

Please share your thoughts on leveraging CCR feature for setting up an A/B env for applications wherein ingest downtime (for A env) is acceptable.

I understand that "follower" cluster in CCR is a read-only replica of the master. Hence it may not be a true A/B setup wherein both A and B setups are accepting writes.

In most of the search apps that I have worked with, search availability is of utmost importance as compared to ingest/write availability. Hence for such apps that can accept some ingest downtime, CCR may be a good option to set up an A/B env.

Your thoughts or experiences?

---

<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:** [March 19, 2019, 5:31pm UTC](https://discuss.elastic.co/t/leveraging-ccr-for-a-b-cluster-setup/169081/2 "2019-03-19T17:31:39Z")

</div>

Closed on March 19, 2019, 5:31pm UTC

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