Bug 921491 - org.infinispan.transaction.WriteSkewException: Detected write skew (random failure)
Summary: org.infinispan.transaction.WriteSkewException: Detected write skew (random fa...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Clustering
Version: 6.1.0,6.3.0
Hardware: i386
OS: Linux
unspecified
high
Target Milestone: ---
: EAP 6.4.0
Assignee: Tristan Tarrant
QA Contact:
URL:
Whiteboard: Infinispan testsuite
Depends On: 915591
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-03-14 10:28 UTC by Jitka Kozana
Modified: 2014-10-25 12:02 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 915591
Environment:
Last Closed: 2014-08-29 14:29:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-2771 0 Major Resolved WriteSkewTest.testWriteSkewWithOnlyPut fails randomly 2016-02-22 11:13:07 UTC

Comment 3 Richard Janík 2013-04-02 11:48:00 UTC
Test org.infinispan.api.mvcc.repeatable_read.WriteSkewTest.testWriteSkewWithOnlyPut fails intermittently with ER3 and Infinispan 5.2.5.Final as well.

Comment 4 JBoss JIRA Server 2013-07-10 10:37:43 UTC
Pedro Ruivo <pedroruivo2> updated the status of jira ISPN-2771 to Coding In Progress

Comment 5 JBoss JIRA Server 2013-07-16 11:52:44 UTC
Pedro Ruivo <pedroruivo2> updated the status of jira ISPN-2771 to Reopened

Comment 6 JBoss JIRA Server 2013-07-16 11:52:44 UTC
Pedro Ruivo <pedroruivo2> made a comment on jira ISPN-2771

This test is still failing because it performs the local write skew check during the copyForUpdate(). Solutions:

easy: don't perform the local write skew check in the copyForUpdate because it will be performed in the prepare phase anyway.
complex: the correct behavior here is to perform the local write skew check when
 * the key has previous read || the command does not ignore the return value

try to do a test case for this race condition...

Comment 7 JBoss JIRA Server 2013-07-18 09:28:04 UTC
Dan Berindei <dberinde> made a comment on jira ISPN-2771

[~pruivo] why is the second approach more correct than the first? Shouldn't one write skew check be enough?

Comment 8 JBoss JIRA Server 2013-07-18 09:42:24 UTC
Pedro Ruivo <pedroruivo2> made a comment on jira ISPN-2771

[~dan.berindei] don't miss understand me. I think the most correct is only to perform the write skew check at prepare time (as it is done in clustered mode).

Comment 10 Paul Ferraro 2014-08-29 14:29:34 UTC
Already fixed upstream.


Note You need to log in before you can comment on or make changes to this bug.