Bug 1043434 - L1 entry added by ST when already invalidated
Summary: L1 entry added by ST when already invalidated
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Data Grid 6
Classification: JBoss
Component: Infinispan
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER2
: 6.3.0
Assignee: Tristan Tarrant
QA Contact: Martin Gencur
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-16 10:14 UTC by Radim Vansa
Modified: 2015-01-26 14:04 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
In distributed cache mode with L1 enabled and <code>onRehash=true</code>, when an entry is overwritten during state transfer, the overwrite may be ignored. This node will then report an outdated value of the entry, and after L1 timeout this entry will be completely removed. </para> <para> As a workaround, use L1 with <code>onRehash=false</code>.
Clone Of:
Environment:
Last Closed: 2015-01-26 14:04:53 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-3838 0 Critical Resolved L1 entry added by ST when already invalidated 2015-05-13 02:03:47 UTC

Description Radim Vansa 2013-12-16 10:14:35 UTC 
Non-transactional cache with L1 enabled. Node A is losing ownership of an entry, the entry is not removed during ST but is going to L1.

1. ST builds the invalidation command, EntryWrapping interceptor starts committing all the entries
2. Write on primary owner (B) occurs
3. A gets the InvalidateL1Command, removes the ImmortalCacheEntry from data container (as it does not own the entry anymore)
4. The ST invalidation command commits the MortalCacheEntry with old value, storing it into the data container.

Result: Outdated value is in L1 cache.
Comment 2 JBoss JIRA Server 2013-12-16 14:09:11 UTC 
William Burns <wburns> updated the status of jira ISPN-3838 to Coding In Progress
Comment 4 Radim Vansa 2014-05-23 06:32:48 UTC 
L1OnRehash was removed, this cannot happen again.
Note You need to log in before you can comment on or make changes to this bug.