]
RH Bugzilla Integration commented on ISPN-5613:
-----------------------------------------------
Tristan Tarrant <ttarrant(a)redhat.com> changed the Status of [bug
Replication timeouts should show more information of the affected
entries
-------------------------------------------------------------------------
Key: ISPN-5613
URL:
https://issues.jboss.org/browse/ISPN-5613
Project: Infinispan
Issue Type: Enhancement
Components: Core
Reporter: Wolf-Dieter Fink
Assignee: Dan Berindei
Typical timeouts for replication are
ERROR [org.infinispan.interceptors.InvocationContextInterceptor] (remote-thread-595)
ISPN000136: Execution error: org.infinispan.util.concurrent.TimeoutException: Replication
timeout for jboss####-#####
and
ERROR ....
Caused by: org.infinispan.util.concurrent.TimeoutException: Node jboss####-##### timed
out
The issue is that it is not possible to check what key/entry is affected.
The cache can become inconsistent between nodes.
There should be an information which key is affected.
For some operations it is not possible at all as there is no information about the
entries (i.e. commit) or the key is binary or custom without a valid toString() method.