Hi all, We have a problem with Geode WAN replication when GW receivers are configured with the same hostname-for-senders and port on all servers.
The reason for such a setup is deploying Geode cluster on a Kubernetes cluster where all GW receivers are reachable from the outside world on the same VIP and port. Other kinds of configuration (different hostname and/or different port for each GW receiver) are not cheap from OAM and resources perspective in cloud native environments and also limit some important use-cases (like scaling). The problem experienced is that shutting down one server is stopping replication to this cluster until the server is up again. We suspect this is because Geode incorrectly assumes there are no more alive servers when just one of them is down (since they share hostname-for-senders and port). Has anyone experienced a similar problem configuring Geode WAN replication in cloud native environments? Thinking about possible solutions in Geode code, our proposal would be to expand internal data in locators with enough information to distinguish servers in the beforementioned use case. The same intervention is likely needed in the client pools and possibly elsewhere in the source code. Any comments about this proposal is welcome. Thanks in advance! Alberto B.
