Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-5613

Replication timeouts should show more information of the affected entries

    Details

      Description

      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.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                dan.berindei Dan Berindei
                Reporter:
                wdfink Wolf-Dieter Fink
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: