[jira] [Commented] (IGNITE-12603) Questions regarding Data Availability/Replication.

["Ilya Kasnacheev (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/IGNITE-12603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17028836#comment-17028836 ] 

Ilya Kasnacheev commented on IGNITE-12603:
------------------------------------------

Please use user@ignite.apache.org mailing list or Stack Overflow to ask Ignite-related questions. JIRA is strictly for development process.

> Questions regarding Data Availability/Replication.
> --------------------------------------------------
>
>                 Key: IGNITE-12603
>                 URL: https://issues.apache.org/jira/browse/IGNITE-12603
>             Project: Ignite
>          Issue Type: Wish
>            Reporter: Aditya
>            Priority: Blocker
>
> 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. I will tell you why it's used later.
> So there are three nodes here running -> CN1, SN1, SN2.
> Question 1:
> We don't use Apache Ignite for cache purposes, but we will use it for disk
> persistent storage. And we don't need Ignite for partitioning data (we will
> think about it later). 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 usually should not make connections with SN2 (since it's backup).
> 2. SN1 and SN2 link will be very fragile and of less bandwidth. Usually,
> both will be in different network segments.
> Question 2:
> Let's say SN1 is down. Now, will the queries automatically reach SN2 without
> doing anything? And if SN1 is restarted, can we expect the queries to reach
> SN1 instead of SN2, as CN1 - SN2 link is slow?
> Question 3 :
> 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?
>  
> PS: We are using JDBC Thin Client, so if possible please answer in that context with examples.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)