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: http://apache-ignite-users.70518.x6.nabble.com
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
CL
This DR feature is what you are looking for, complete solution:
https://www.gridgain.com/docs/latest/administrators-guide/data-center-replication/introduction
On Sunday, December 6, 2020, Alexandr Shapkin wrote:
> Hi,
>
>
>
> I don’t think that ignite support this out of the box, cause data
> re
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
