ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From userx <gagan...@gmail.com>
Subject CacheMode - REPLICATED related questions
Date Sat, 26 Aug 2017 06:09:07 GMT

Consider the following situation

Machine M1-> Data Grid Server S1
Machine M2-> Data Grid Server S2
Machine M3-> Data Grid Server S3

I intend to use REPLICATED mode because data loss is something which my
application can't take. 


Is there a way, we can identify which out of the three machines will be the
PRIMARY mode ? And does it change w.r.t different clients, say if C1 is
doing put, the primary is M1 and if C2 is doing put the primary is M2. The
reason I am asking this question is if replication fails for C1 and say M1
goes down for some reason, then even if M2 and M3 are there, they are not
serving any purpose. 

Can we configure or designate say M1 always to be primary ?

We have one of the CacheWriteSynchronizationMode as PRIMARY_SYNC which means
that put operation will wait for data to be written on PRIMARY NODE (say
M1)? Is there a way that we ensure data to be replicated atleast 2 out of
the 3 machines listed. I could see the options as FULL_SYNC or PRIMARY_SYNC
so its either all of them or just the primary one.

What happens if REPLICATION activity fails ? Is there any documentation for
the same as to what the cluster does in such cases or does client have to
take any actions on its part say log etc ?

I am soon going to enter production with Xmx as 1G and "Persistent Store
Enabled" to take care of data to be cached whose size > 1G. Your
https://apacheignite.readme.io/docs/preparing-for-production document has
mentioned the JVM related settings for a server with Xmx of 10G. Since I am
going with 1G, is there a documentation which helps me w.r.t recommended
settings on Xmx of 1g ?

View this message in context: http://apache-ignite-users.70518.x6.nabble.com/CacheMode-REPLICATED-related-questions-tp16423.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

View raw message