Hi Alex
This got ignored for a while
But the known drawbacks of this approach, can you please let me know as I
need to finalize an approach on how to route requests to secondary site if
primary is not in working condition etc
Thanks
--
Sent from:
HI
We have no issue with the data replication, we do have feeder services
feeding data into multiple clusters real time.
And, we are going to have active active set up only, but secondary is only
used in case primary has any issues.
At the moment, consumers use the full connection string like
h
> 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
> *Sent: *Sunday, December 6, 2020 2:47 PM
> *To: *u
to resolve the nameto, 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: NaveenSent: Sunday, December 6, 2020 2:47 PMTo: user@ignite.apache.orgSubject: Implementing HA among Ignite Clusters Hi All We have 2 clusters
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
