Hi, I don’t think that ignite support this out of the box, cause data replication is something beyond the default distribution. The usage depends on how your data is replicated, whether you want active-active synchronization, and so on. But if it’s about switching from one cluster to another, and always using a single cluster at a time, something like dynamic DNS or a custom load balancer should work here. I.e. you can configure your consumers to access domain my.cluster.com that resolves to the primary cluster, IP=192.168.1.1. When you want to switch the load, you can adjust your DNS to resolve the name to, say, IP=192.168.1.13 which means the secondary one. This approach has some drawbacks but is quite simple to use and straightforward. From: Naveen Hi All We have 2 clusters (Primary and secondary) running and both are always in sync from data perspective. Always consumers are using Primary only, but when primary is not reachable, it should get redirected to secondary cluster How can this be achieved ? 1. Can we do anything on the cluster side which will take care of this, like with config changes on the primary cluster like changing the connecton string etc. Like some of the messaging products uses connection URLs like tcp://server1||tco://server2 something like this, if server1 is not reachable, it will get routed to server2. Somehing like this can be done here ? 2. DOing this from consumer side only, as and when they get exceptions like disconnect etc, try connecting it to secondary and vice versa What are the options we have for this scenario Thanks Naveen -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/ |
- Implementing HA among Ignite Clusters Naveen
- RE: Implementing HA among Ignite Clusters Alexandr Shapkin
