Hi,

Yes it is for replication.

Actually, when it tries to create a cache with the Total Order based 
protocol, it checks if the sequencer is in JGroups' protocol stack. If 
it is not, then an exception is thrown.

Cheers,
Pedro

On 3/6/12 1:47 PM, Bela Ban wrote:
> No, I think this is a good idea. The algorithm should check if SEQUENCER
> is present in the stack, and insert a new instance at startup if not,
> otherwise no-op.
>
> This is only for *replication*, correct ? For *distribution*, the
> CloudTM folks will send us a different total order protocol (TOM)
> soon... but the same mechanism can be applied.
>
> On 3/6/12 12:58 PM, Mircea Markus wrote:
>> Hi,
>>
>> Total order requires JGroup's SEQEUNCER[1] protocol to be added to the 
>> protocol stack. So users that want to switch between e.g. total order and 
>> optimistic TX are required to also change the jgroups config (and the other 
>> way around). This is not very user friendly, so I'm thinking to try and 
>> insert the SEQUENCER if it is missing from the stack and TotalOrder is 
>> enabled, together with a log message. Anyone sees any problem with this? 
>> Bela?
>>
>> [1] http://www.jgroups.org/javadoc/org/jgroups/protocols/SEQUENCER.html
_______________________________________________
infinispan-dev mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/infinispan-dev

Reply via email to