Bug 1025258

Summary:	When L1.onRehash is enabled, L1 invalidations should be sent to the previous owners
Product:	[JBoss] JBoss Data Grid 6	Reporter:	Radim Vansa <rvansa>
Component:	Infinispan	Assignee:	Tristan Tarrant <ttarrant>
Status:	CLOSED UPSTREAM	QA Contact:	Martin Gencur <mgencur>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	jdg-bugs
Target Milestone:	ER4
Target Release:	6.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
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.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:28:52 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:	1017190

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

Comment 3 Red Hat Bugzilla 2025-02-10 03:28:52 UTC

This product has been discontinued or is no longer tracked in Red Hat Bugzilla.