Re: [infinispan-dev] X-S replication configuration
On 9 Aug 2012, at 18:28, Erik Salter wrote:
Resurrecting this thread for a minute (insert "Walking
Dead" reference here)
-- there are two configuration operations -- sync and async.
Are these related to transaction replay? For instance, in the case of a
transaction, does a "sync" configuration mean the cluster will replay a 2PC
(or 1PC, in the case of synchronizations) to the other sites?
In the first iteration yes. Further on we can think about other ways of optimising this,
e.g. if the 2nd site is passive, then sending only a 1PC should be good enough.
And async
means "fire and forget?"
Initially yes. The plan is to add some store and
fwd capability at a further point, so it would be more like "fire and eventually
deliver".
Plus if I have the following configuration:
<namedCache="cache1">
<backup name="STL" strategy="sync"/>
<backup name="SFO" strategy="async"/>
</namedCache>
<namedCache="cache2">
<backup name="STL" strategy="sync"/>
<backup name="SFO" strategy="async"/>
</namedCache>
<namedCache="cache1">
<backup name="STL" strategy="sync"/>
<backup name="SFO" strategy="async"/>
</namedCache>
cache1 is defined twice, I guess this was a copy-paste thing?
<namedCache="cache3">
<backup name="STL" strategy="async"/> <---------
<backup name="SFO" strategy="async"/>
</namedCache>
...what happens if cache1, cache2, and cache3 were started in a transaction
in the PHL site? How would these be replayed on the backup sites? I would
expect that it would be "sync" for STL and "async" for SFO.
yes.
Thanks,
Erik
-----Original Message-----
From: infinispan-dev-bounces(a)lists.jboss.org
[mailto:infinispan-dev-bounces@lists.jboss.org] On Behalf Of Vladimir
Blagojevic
Sent: Monday, July 16, 2012 12:17 PM
To: infinispan -Dev List
Cc: Erik Salter (esalter)
Subject: Re: [infinispan-dev] X-S replication configuration
On 12-07-12 8:47 AM, Mircea Markus wrote:
> On 10 Jul 2012, at 18:28, Galder Zamarreño wrote:
>>
>> And line 25: <backups> instead of <sites>
Same here. I would keep sites in global definition and backups in
caches. But either way is good, matter of taste!
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev