[infinispan-dev] Time for a new NBST thread

[Manik Surtani]

On 28 May 2012, at 15:59, Dan Berindei wrote:

> Hi guys
> 
> I published a new version of the non-blocking state transfer design
> document here:
> https://community.jboss.org/wiki/Non-blockingStateTransfer
> 
> This time I focused a bit on the "other" cache configuration (other
> than dist-sync, that is). This revealed some new problems, these are
> the most interesting ones:
> * With async-commit phase or async-1pc, we can get stale locks on
> joiners. I have an Infinispan-only approach that should work, but it
> may be easier to just require FLUSH.

I would prefer not to have to use FLUSH since FLUSH "stops the world".  Even for nodes not participating in the state transfer.

> * Async-commit + recovery enabled: a node sends a commit command to 2
> owners, one node loses the message, and then the originator dies
> before retransmitting. How do we let the TM know that the transaction
> is in-doubt, since to the TM it looks like it has been committed?
> 
> Please try to read the document and let me know if anything sounds too
> opaque or doesn't make sense. I think it's good enough for starting
> the implementation, although I've removed the actual implementation
> details from the document for now.

Will do.	

> 
> Cheers
> Dan
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev

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

Lead, Infinispan
http://www.infinispan.org