We currently have CCR setup between two deployments within Elastic Cloud.
The main reason for having this configuration is that we write heavily to the leader, and don't mind a search performance hit there, but would like to maintain search speed on the follower.
When the follower is initialised, the performance on that cluster holds up well. When we have a load of writes to the leader however, we see a massive spike in CPU usage on the follower.
There are the the default follow values you can configure, but I can't find a configuration that gives me this desired result? Any advice?