[infinispan-issues] [JBoss JIRA] (ISPN-5545) Make lazy near caching more selective

[Galder Zamarreño (JIRA)]

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

Galder Zamarreño commented on ISPN-5545:
----------------------------------------

Note: There might be situations where due to the volume of keys, it would be more optimal to just receive invalidation messages for all keys rather than having to having to negotiate at runtime the keys for which the client is interested. So, the option to receive events on all keys is still useful. This option would be most useful when the near cache contains close to the entire subset of keys as the backend servers.

> Make lazy near caching more selective
> -------------------------------------
>
>                 Key: ISPN-5545
>                 URL: https://issues.jboss.org/browse/ISPN-5545
>             Project: Infinispan
>          Issue Type: Enhancement
>            Reporter: Galder Zamarreño
>            Assignee: Galder Zamarreño
>
> In the current form, when lazy near caching is enabled, the server sends invalidation messages for any key that has been created, modified or removed.
> This is suboptimal for a couple of reasons:
> 1. First of all, a near cache is only interested in receiving invalidation events for those keys that are currently stored in the near cache. There needs to be a way to be able to narrow the events sent from the server to this subset of keys.
> 2. Lazy near caches do not care about created events. If an entry is present in the near cache, it has already been created, so it's only interested in modified and removed events. There needs to be a way to narrow this down too.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)