• Type: Feature Request
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 8.2.8.Final, 9.1.1.Final, 9.2.0.Alpha2
    • Fix Version/s: 9.2.0.Beta1, 9.2.0.Final
    • Component/s: Hibernate Cache
    • Labels:
    • Environment:

      WildFly 10.1.0, WildFly 11.0.0.CR1, WildFly master, Hibernate 2LC


      Infinispan currently does not seem to implement an efficient way to clear an entire cache cluster-wide. This forces Hibernate to remove all entries one by one when a cache region needs to be cleared, for example when a buld CriteriaUpdate or CriteriaDelete is used.

      The behavior we are observing is:

      1. All nodes in the cluster are queried for the keyset in a region
      2. A lock seems to be in place for this region for the duration of the commit
      3. The initiating node constructs a message with InvalidateCommands for all keys
      4. This large message (230MB for 200k entries) is sent to all nodes in the cluster

      For large caches this can take very long. We had to increase the remote-timeout to 60 seconds to prevent timeouts. During this time, the entire cluster is locked an busy processing the cache invalidations. As you can understand, this is not a workable solution for us. On some places we can prevent the cache clear by updating the records one by one, but in other places this is not an option.

      The corresponding report at Hibernate can be found here:

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  rvansa Radim Vansa
                  papegaaij Emond Papegaaij
                • Votes:
                  1 Vote for this issue
                  3 Start watching this issue


                  • Created: