[infinispan-issues] [JBoss JIRA] (ISPN-1841) Write skew checks are performed on all entries in a transaction context
Manik Surtani (JIRA)
jira-events at lists.jboss.org
Sat Feb 4 12:13:48 EST 2012
Manik Surtani created ISPN-1841:
-----------------------------------
Summary: Write skew checks are performed on all entries in a transaction context
Key: ISPN-1841
URL: https://issues.jboss.org/browse/ISPN-1841
Project: Infinispan
Issue Type: Bug
Components: Test Suite
Reporter: Manik Surtani
Assignee: Mircea Markus
Fix For: 5.0.2.FINAL, 5.2.0.ALPHA1
They should only be performed on entries that are read first and then updated. The current implementation doesn't cause any problems, however it is unnecessary processing and certain transactions may unnecessarily abort if, for example, an entry is read, and not written to, but the entry changes before the transaction commits.
>From Pedro Ruivo's email to infinispan-dev, where this was reported:
{quote}
I've noticed that in the last version (5.1.x) the write skew check is
performed on all keys written. However, from your documentation [1] I
understood that the write skew was meant to be performed only on the
written keys that were previously read.
Is this change intentional?
Cheers,
Pedro Ruivo
[1] https://docs.jboss.org/author/display/ISPN51/Data+Versioning
"Write skew checks are performed at prepare-time to ensure a concurrent
transaction hasn't modified an entry while it was read and potentially
updated based on the value read."
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list