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

[Emond Papegaaij (JIRA)]

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

Emond Papegaaij commented on ISPN-8411:
---------------------------------------

Well, the warning is not very clear in the outcome of the conflict, so we decided to be on the safe side and fix the warnings. Perhaps the warning should reflect the concurrency strategy used, like: _"Requesting TRANSACTIONAL cache concurrency strategy but the cache is not configured as transactional. The resulting cache will not be transactional."_

To fix the warnings, we had to change our {{persistence.xml}} to include the {{default_cache_concurrency_strategy}} and update all {{@Cache}} annotations on {{@OneToMany}} properties. {{org.hibernate.annotations.Cache}} has no default for the {{usage}} attribute, so to enable caching on a collection you must specify the concurrency strategy. On entities you can use {{@Cacheable(true)}} (or enable it globally, as we did). Perhaps the {{Cache.usage}} attribute could benefit from a {{DEFAULT}} concurrency strategy, which could also be the default value of the attribute.

> 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)