<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On 2 Nov 2011, at 22:43, Paolo Romano wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div bgcolor="#FFFFFF" text="#000000">
Cool stuff Mircea! ;-)<br></div></blockquote>Thanks :-)<br><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000">
We're actually planning for rebasing our total-order based schemes
on this pull, so we look forward to seeing it finalized!<br>
<br>
Have you already implemented any mechanism to avoid consistency
issues related to inversions of the delivery order of commit
messages at different replicas (I mentioned it in some past mail)? <br></div></blockquote>yes, the approach we took was for the node where transaction originated to only release locks (async) after commit is completed. In other words the commit message no longer releases locks but there's an additional async call that would do that after commit finishes.<br><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000">
<br>
Actually, after a second thought I realized that if you only care
about eventual consistency you could use a simple scalar clock
incremented independently at each primary owner to order the commit
events across the non-primary nodes (using the Thomas Write Rule [1]
to avoid any blocking).</div></blockquote>I'll give it a thought - thanks again for the feedback!<br><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000">
<br>
Then, if you want to raise the bar of consistency you would need at
least causal order among transactions... this is something that is
actually in our short term roadmap, along with and a new, highly
scalable (not relying on any global clock) serializable MVCC
algorithm... more on this soon! ;-)</div></blockquote><blockquote type="cite"><div bgcolor="#FFFFFF" text="#000000">
<br>
Cheers,<br>
<br>
Paolo<br>
<br>
[1] <a class="moz-txt-link-freetext" href="http://en.wikipedia.org/wiki/Thomas_write_rule">http://en.wikipedia.org/wiki/Thomas_write_rule</a><br>
<br>
On 11/2/11 9:21 PM, Mircea Markus wrote:
<blockquote cite="mid:E29401F9-5A26-43EC-9AF8-FDA57BE87B33@jboss.com" type="cite">Hi guys,
<div><br>
</div>
<div>The single lock owner stuff is ready for review. It's a
massive change so I'd expect the review process to take some
days. Can you please take a look and comment?</div>
<div><br>
</div>
<div>JIRA is: <a moz-do-not-send="true" href="https://issues.jboss.org/browse/ISPN-1137">https://issues.jboss.org/browse/ISPN-1137</a></div>
<div><br>
</div>
<div>Pull request: <a moz-do-not-send="true" href="https://github.com/infinispan/infinispan/pull/574">https://github.com/infinispan/infinispan/pull/574</a></div>
<div><br>
</div>
<div>Thanks!</div>
<div><br>
</div>
<div>Mircea</div>
<div><br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
infinispan-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a>
<a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/infinispan-dev">https://lists.jboss.org/mailman/listinfo/infinispan-dev</a></pre>
</blockquote>
<br>
</div>
_______________________________________________<br>infinispan-dev mailing list<br><a href="mailto:infinispan-dev@lists.jboss.org">infinispan-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/infinispan-dev</blockquote></div><br></body></html>