Bug 1243953

Summary:	Replication timeouts should show more information of the affected entries
Product:	[JBoss] JBoss Data Grid 6	Reporter:	wfink
Component:	Infinispan	Assignee:	Tristan Tarrant <ttarrant>
Status:	CLOSED UPSTREAM	QA Contact:	Martin Gencur <mgencur>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.5.0	CC:	dereed, jdg-bugs, vjuranek
Target Milestone:	ER1
Target Release:	6.6.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-02-10 03:47:53 UTC	Type:	Enhancement
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description wfink 2015-07-16 16:37:10 UTC

Description of problem:
If there are timeout problems during replication the cache can become inconsistent for different nodes.
But there is no information which entries are affected.


There should be a warning for the inconsistency and an information which key is affected to be able to do a cleanup.

Comment 1 wfink 2015-07-16 16:39:49 UTC

For the different commands it might not possible to provide that information.
Also it might not possible to print a useful information if the key is a binary value or did not contain a useful toString() method for custom classes.

Comment 2 dereed 2015-07-16 17:13:59 UTC

Some log messages already print the key (such as lock timeouts), so that part shouldn't be an issue.

Comment 3 Dan Berindei 2015-11-02 13:11:21 UTC

PR: https://github.com/infinispan/jdg/pull/775

Comment 4 Vojtech Juranek 2015-11-12 15:28:18 UTC

Error log records now contains affected keys, log record looks like this (in this case the key was byte array so strange key name is expected:-)

Error executing command PutKeyValueCommand, writing keys [[B@232f4a48]: org.infinispan.util.concurrent.TimeoutException: Replication timeout for server1/clustered

Comment 7 Red Hat Bugzilla 2025-02-10 03:47:53 UTC

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