Thanks jose for the prompt reply.

Based on what you reply, I can understand that using DriverManager I can
query a particular node. But my question is regarding replication and data
availability. So, please let me rephrase my question.

Scenario:

Datacenter 1 (Main) -> One Application Server (Client Node CN1) and One DB
Server (Server Node SN1).

Datacenter 2 (Recovery) -> One Application Server (Client Node CN2) and One
DB Server (Server Node SN2).

Usually all the user requests go to CN1 but not CN2. So, technically we will
not run CN2. So forget about CN2. Will tell why it's used later.

So there are three nodes here running -> CN1, SN1, SN2.

Question1:

I don't use Apache Ignite for cache purpose, but we will use it for disk
persistent storage. Now, how to make sure that the data that is being stored
in SN1 will be replicated to SN2. We want SN2 to be backup node for SN1. Is
that possible? If so, how?

Conditions:

1. CN1 will not make connections to SN2.
2. SN1 and SN2 link will be very fragile and of less bandwidth.


Question2 :

After a few months, we will flip the entire setup, making DC2 as Main and
DC1 as Recovery. In this case, CN2 will make connections to SN2 and CN1 will
not be running. How to quickly switch so that SN2 is replicated almost with
SN1 and be ready to serve requests from CN2?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Reply via email to