[
https://issues.jboss.org/browse/ISPN-5545?page=com.atlassian.jira.plugin....
]
Galder Zamarreño updated ISPN-5545:
-----------------------------------
Description:
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 might only interested in receiving invalidation events for
those keys that are currently stored in the near cache. If the near cache is small subset
of the entire cache, having such option would vastly reduce the number of events sent to
clients. So, 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.
was:
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.
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 might only interested in receiving invalidation events for
those keys that are currently stored in the near cache. If the near cache is small subset
of the entire cache, having such option would vastly reduce the number of events sent to
clients. So, 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)