Bug 1185779

Summary: Transaction cannot be recommitted in new topology
Product: [JBoss] JBoss Data Grid 6 Reporter: Radim Vansa <rvansa>
Component: InfinispanAssignee: Dan Berindei <dberinde>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Gencur <mgencur>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: chuffman, dmehra, jdg-bugs, mcimbora, pzapataf, rmarwaha, slaskawi
Target Milestone: ER2   
Target Release: 6.4.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
In Red Hat JBoss Data Grid, each transaction can be executed on each node only once. When a transaction affects multiple entries, one of them owned and another not owned, only the owned entry is modified during execution. However, if there is a topology change (change of entry ownership) during the transaction, the node may become owner of some entry while receiving old (pre-transaction) value via the state-transfer. The transaction should execute again on the newly owned entries, but it does not so since it is already marked as completed. The consequence is stale value on some nodes.
Story Points: ---
Clone Of:
: 1202341 (view as bug list) Environment:
Last Closed: 2015-04-02 12:13:42 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:    
Bug Blocks: 1202341    

Description Radim Vansa 2015-01-26 09:42:37 UTC
See JIRA. General issue (not limited to split-brain). Consequence is stale entry.

Comment 4 JBoss JIRA Server 2015-02-06 09:10:44 UTC
Dan Berindei <dberinde> updated the status of jira ISPN-5174 to Coding In Progress