Infinispan cache is definitely desynchronized after network trouble

Solution Unverified - Updated -

Issue

  • Network failure causes temporary cluster split and re-join
  • During the cluster split at least some nodes can still process requests, so that local cache content changes
  • After the cluster member re-join the defined Infinispan replicated-caches don't perform a merge
  • Results of this behavior: The content of every replicated-cache becomes un-reliable when
    • a cluster splits due to network trouble
    • stays un-reliable even after a re-join, as no merge is triggered.

Environment

  • JBoss Enterprise Application Platform (EAP) 6
    • Infinispan

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.