Hi Girard,
You can mix replicated & non-replicated though the non-replicated can't
have a "partition" data policy. I think it's most common to use data
policy "empty" or "preloaded" in members that don't use a "replicate"
data policy.
All members have to use the same "scope", so if a member already has a
cache region with "distributed-ack" scope and another member tries to
instantiate the same region with a "global" scope it will be rejected.
Le 8/6/2015 12:52 AM, GIRARD-REYDET Vincent a écrit :
It’s not clear to me what the “Can be mixed with replication … some
holding non-replicas” part means exactly. I understand that you can
mix replication and non-replication, but I’m not sure if it’s in the
same region (on different servers) or not.
In other words, if I go for “Replicated (distributed)”, do I have to
use it on all members defining this region, with the same distribution
mode? Or can I have, for a region A, some members using Replicated
(distributed) = always storing all values, and some other members
using Distributed non-replicated = only getting the data they are
interested to? See picture attached for an example : can member M3
define region A with only a “register interest” (this would be weird) ?
