Leveraging CCR for A/B cluster setup

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?

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