[infinispan-dev] ISPN-263 and handling partitions

Manik Surtani msurtani at redhat.com
Tue Apr 23 13:26:06 EDT 2013


On 23 Apr 2013, at 16:37, Bela Ban <bban at redhat.com> wrote:

> 
> 
> On 4/22/13 6:46 PM, Manik Surtani wrote:
>> 
>> On 22 Apr 2013, at 16:46, Mircea Markus <mmarkus at redhat.com> wrote:
>> 
>>> would the read only partition be wiped out and repopulated during
>>> merge?
>> 
>> Naively, yes.  But as Dan pointed out, if a key K only exists in the
>> minor partition (primary and backups), then just wiping the minor
>> partition nodes will result in data loss.
>> 
>> A more sophisticated algorithm would just wipe keys in the minor
>> partition that also exist in the major partition.
> 
> 
> I think this would be good enough for a lot of scenarios.
> 
> 
>> An *even* more sophisticated algorithm would only wipe keys in the
>> minor partition that also exist in the major partition, that have
>> changed since the partition occurred.  Hence the vector clocks.
> 
> Even better. What would you do in a conflict case ? Throw the conflict 
> at the user who has to resolve it ? Always prefer the data from the 
> primary partition ?

Why would a conflict happen?  Only the primary partition is allowed to update data after a split.

- M
--
Manik Surtani
manik at jboss.org
twitter.com/maniksurtani

Platform Architect, JBoss Data Grid
http://red.ht/data-grid




More information about the infinispan-dev mailing list