Bug 1019742 - Out of data read after write on node losing ownership
Summary: Out of data read after write on node losing ownership
Keywords:
Status: VERIFIED
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER4
: 6.2.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks: 1017190
TreeView+ depends on / blocked
 
Reported: 2013-10-16 10:42 UTC by Radim Vansa
Modified: 2023-03-02 08:28 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
During the cluster rebalance process, after a node joins or leaves the cluster, a read operation may retrieve data that has already been overwritten. The behavior was observed in transactional mode but may not be limited to it.
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-3635 0 Critical Resolved Out of data read after write on node losing ownership 2014-03-25 01:36:19 UTC

Description Radim Vansa 2013-10-16 10:42:43 UTC
In a situation where a node is losing ownership of an entry (during a state transfer), when the node does a write (and commits that), the change is propagated only to the new owners, the entry is not written locally. However, when it executes read for this key afterwards, it gets the old value as this is directly retrieved from the data container.

Note that the entry should not be written locally if the invalidation was already executed.

This bug was observed in transactional mode, but might not be limited to it.

Comment 2 JBoss JIRA Server 2013-10-18 09:45:33 UTC
Pedro Ruivo <pedroruivo2> updated the status of jira ISPN-3635 to Coding In Progress


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