Bug 915591
Summary: | org.infinispan.transaction.WriteSkewException: Detected write skew (random failure) | ||||||
---|---|---|---|---|---|---|---|
Product: | [JBoss] JBoss Data Grid 6 | Reporter: | Vitalii Chepeliuk <vchepeli> | ||||
Component: | Infinispan | Assignee: | Tristan Tarrant <ttarrant> | ||||
Status: | VERIFIED --- | QA Contact: | Martin Gencur <mgencur> | ||||
Severity: | high | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.1.0 | CC: | jdg-bugs, jkudrnac | ||||
Target Milestone: | DR2 | ||||||
Target Release: | 6.2.0 | ||||||
Hardware: | sparc64 | ||||||
OS: | Solaris | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | |||||||
: | 921491 (view as bug list) | Environment: | |||||
Last Closed: | 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: | |||||||
Bug Blocks: | 921491 | ||||||
Attachments: |
|
Description
Vitalii Chepeliuk
2013-02-26 07:48:21 UTC
Adrian Nistor <anistor> made a comment on jira ISPN-2858 So which test method failed? Could you also attach the trace log please? Created attachment 702832 [details]
Added console output
Adrian Nistor <anistor> made a comment on jira ISPN-2858 From the attached output: {noformat} 2013-02-25 12:55:30,993 ERROR [UnitTestTestNGListener] (testng-WriteSkewTest) Test testWriteSkewWithOnlyPut(org.infinispan.api.mvcc.repeatable_read.WriteSkewTest) failed. {noformat} This is a duplicate of ISPN-2771. Adrian Nistor <anistor> updated the status of jira ISPN-2858 to Resolved 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). |