Hi folks, we are looking to deploy our stack to 2 different AWS regions for high availability in case one region goes dark for any period of time. I have gotten a cluster up and replicating across the 2 regions over a site-to-site VPN tunnel, with a master in one region communicating with data nodes residing in each region.
I had thought initially that we could have the stack in each region point to the ES nodes in the same region, but now I am discovering that ES does some internal load balancing which would mean that a stack in one region could potentially communicate with the ES nodes in the other region which could cause unwanted latency.
I am curious if this is a concern? I am not exactly sure how the internal load balancing works (latency based? least conn?). If this is a concern, what options do I have in regards to replicating between 2 separate clusters? And yes, I have read this is not advised. We are not really worried about replication lag as the updates to our indices will be minimal.