[infinispan-dev] asynchronous change manager for high load Lucene
Bela Ban
bban at redhat.com
Mon Mar 29 11:16:01 EDT 2010
Emmanuel Bernard wrote:
>> In other words, if we have to apply a change across a cluster, with 1
>> message, total order can replace a two-phase lock-unlock protocol.
>
> In Lucene's term that would mean that an index copy is present on all
> nodes (not store in Infinispan necessarily) and all changes are passed
> and executed on all nodes (being passed in total ordering via JGroups).
Ah, that changes the game ! I thought that the index is some kind of
metadata, present on every node. Of course, if that'snot the case, then
SEQUENCER makes no sense...
--
Bela Ban
Lead JGroups / Clustering Team
JBoss
More information about the infinispan-dev
mailing list