> On Nov 29, 2019, at 3:14 AM, Alberto Bustamante Reyes > <alberto.bustamante.re...@est.tech> wrote: > > 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.
Are you using LoadBalancer Service type? > 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). If you could somehow configure host and port for sender (code modification required) would exposing each port through the LoadBalancer be too expensive too? > 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). Sees like at the worst case when it tries to reconnect the LB should give it a live server and it think the single server is back up. -Jake
