Bug 921491
| Summary: | org.infinispan.transaction.WriteSkewException: Detected write skew (random failure) | ||
|---|---|---|---|
| Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Jitka Kozana <jkudrnac> |
| Component: | Clustering | Assignee: | Tristan Tarrant <ttarrant> |
| Status: | CLOSED NOTABUG | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1.0, 6.3.0 | CC: | jdg-bugs, jkudrnac, myarboro, paul.ferraro, rjanik, vchepeli |
| Target Milestone: | --- | ||
| Target Release: | EAP 6.4.0 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | Infinispan testsuite | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 915591 | Environment: | |
| Last Closed: | 2014-08-29 14:29:34 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 915591 | ||
| Bug Blocks: | |||
|
Comment 3
Richard JanÃk
2013-04-02 11:48:00 UTC
Pedro Ruivo <pedroruivo2> updated the status of jira ISPN-2771 to Coding In Progress Pedro Ruivo <pedroruivo2> updated the status of jira ISPN-2771 to Reopened 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... 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? 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). Already fixed upstream. |