[infinispan-issues] [JBoss JIRA] (ISPN-10678) Cluster Expiration Reaper should only expire primary owned entries

[Will Burns (Jira)]

     [ https://issues.jboss.org/browse/ISPN-10678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will Burns updated ISPN-10678:
------------------------------
    Status: Open  (was: New)


> Cluster Expiration Reaper should only expire primary owned entries
> ------------------------------------------------------------------
>
>                 Key: ISPN-10678
>                 URL: https://issues.jboss.org/browse/ISPN-10678
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Expiration
>    Affects Versions: 9.4.16.Final, 10.0.0.CR2
>            Reporter: Will Burns
>            Assignee: Will Burns
>            Priority: Major
>             Fix For: 10.0.0.Final, 9.4.17.Final
>
>
> Today cluster expiration fires for any expired entry it finds. We should instead only expire an entry when it is the primary owner encountering the entry. This will allow expiration to scale much better depending on the number of owners. This also reduces network and locking contention as we may have been sending duplicate expiration commands from backups and primary at the same time.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)