[infinispan-issues] [JBoss JIRA] (ISPN-8411) Add support for efficient removeAll

[Radim Vansa (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-8411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13478142#comment-13478142 ] 

Radim Vansa commented on ISPN-8411:
-----------------------------------

Good point, this should get inlined with the default configuration. Then all the people using transactional caches will get that warning, but at least it may push them in the right direction. Note that the original warning could be safely ignored, TRANSACTIONAL and READ_WRITE strategies offer the same guarantees in Infinispan (Hibernate later on specified that transactional means 'serializable' and read-write 'linearizable', but we're rather on the safe side).

I wonder what changes in your codebase are needed when you configure the server through WF's standalone(-ha).xml

> Add support for efficient removeAll
> -----------------------------------
>
>                 Key: ISPN-8411
>                 URL: https://issues.jboss.org/browse/ISPN-8411
>             Project: Infinispan
>          Issue Type: Feature Request
>          Components: Hibernate Cache
>    Affects Versions: 8.2.8.Final, 9.1.1.Final
>         Environment: WildFly 10.1.0, WildFly 11.0.0.CR1, WildFly master, Hibernate 2LC
>            Reporter: Emond Papegaaij
>            Assignee: Galder Zamarreño
>
> 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:
> # All nodes in the cluster are queried for the keyset in a region
> # A lock seems to be in place for this region for the duration of the commit
> # The initiating node constructs a message with {{InvalidateCommands}} for all keys
> # 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: https://hibernate.atlassian.net/browse/HHH-12036



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)