I have a query like while working with CCR feature everything went well except one use case like
- Placed a document from one cluster, then replicated the same doc in other cluster
- Then the first cluster down, so obviously writes through second cluster and that is also fine
- Now i got a request to update/delete the document, which resides in follower index of second cluster because second cluster is primary. In this case we got 403 operation not allowed.
How we can overcome this scenario with CCR feature? Is there any other alternatives which is capable of handle this usecase, apart from CCR is also fine. It would be great, if you suggest or refer any solution.