[infinispan-dev] NBST design

Galder Zamarreño galder at redhat.com
Wed Aug 15 06:19:48 EDT 2012


More comments:

Leave flow, step 2: "The topology id is not incremented because the new topology does not have state to be transferered with respect to previous topology."

Hmmm, if you have 2 owners for data and one leaves, aren't you gonna have to do some transfering to find a new backup owner for that data?

On Aug 15, 2012, at 11:24 AM, Adrian Nistor wrote:

> Hi,
> 
> I managed to rewrite the old NBST design document and created a v2 [1] 
> that should cover the interesting aspects. I'm not sure I managed to 
> make it intelligible and sound enough, but this is the best I could do 
> after several attempts at rewriting :)
> 
> Please read it. Your feedback is welcome!
> 
> The old document is still there [2] for now but should not be relied 
> upon. I kept it because some parts of it might still be relevant and 
> could be moved to v2 doc, but I don't think they are essential in 
> understading the code of our pull request. Dan, could you have a look if 
> there are any bits that we need to move to v2?
> 
> Thanks,
> Adrian
> 
> [1] https://community.jboss.org/wiki/Non-BlockingStateTransferV2
> 
> [2] https://community.jboss.org/wiki/Non-blockingStateTransfer
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache




More information about the infinispan-dev mailing list