Bug 1025258 - When L1.onRehash is enabled, L1 invalidations should be sent to the previous owners
Summary: When L1.onRehash is enabled, L1 invalidations should be sent to the previous ...
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-31 10:36 UTC by Radim Vansa
Modified: 2018-09-12 22:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
With L1 enabled, after a cluster rebalance following a node joining or leaving, L1 may stay outdated on a node - reads from this node will not reflect further writes to the entry until the entry times out from the L1.
Clone Of:
Environment:
Last Closed:
Type: Bug

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker ISPN-2475 0 Critical Resolved When L1.onRehash is enabled, L1 invalidations should be sent to the previous owners 2014-05-23 06:57:22 UTC

Description Radim Vansa 2013-10-31 10:36:09 UTC 
When L1.onRehash is enabled (by default) and the node loses ownership of some keys, it does not remove them immediately but keeps them in L1. New owners should record this node in L1ManagerImpl.requestors in order to send L1 invalidation when the key is overwritten. However, this is not implemented.

The result is that node may read outdated entry (the cluster is not consistent).

There's a comment about the intended behaviour in StateConsumerImpl, line 385.
Comment 2 JBoss JIRA Server 2013-11-05 21:48:02 UTC 
William Burns <wburns> updated the status of jira ISPN-2475 to Coding In Progress
Note You need to log in before you can comment on or make changes to this bug.