I'm using the lateral cache.
I'll investigate the filter remove by hashcode stuff, although I'm not
certain if all my objects actually define sensible hashcodes.
Thanks, Michael
Aaron Smuts wrote:
Are you using the lateral or the remote cache? The
lateral has a setting called filter remove by hash
code. This prevents removal if the hashcode is the
same. This solves your problem.
If you are using the remote cache then you have a
different situation.
Let's say that B gets an element E from the db and
then adds it to the cache. It goes to R (the remote
cache). The remote cache issues a remove to all the
clients. Clienbt A gets a request for the element E.
It checks its local cache and doesn't have it. A then
checks the remote cache. It finds the element and and
adds it locally. (There is also a setting to add the
element to A when B adds it to the remote cache).
In extremely high traffic scenarios with low hit and
high put rates, I set the local memory size to 0 and
configure the clients of the remote cache to not
receive updates.
Aaron
--- Michael Stevens <[EMAIL PROTECTED]> wrote:
Hi.
Another question about clustered caching and
IssueRemoveOnPut.
I have a clustered cache setup with two machines A
and
B. IssueRemoveOnPut is enabled so that I don't try
to replicate
objects, just ensure obsolete versions are removed
from the cache.
Machine A has object 1 cached.
Machine B has object 1 cached.
Machine A updates object 1 and calls put() to store
the new version.
Machine B receives a remove (from the put), and
removes object 1
from the cache.
Later, Machine B tries to access object id 1, finds
it is uncached,
loads it from the database, and stores it in the
cache by calling
put().
Machine A receives a remove (from the put!), and
removes object 1
from the cache.
Repeat endlessly. How can I stop replacing the
invalidated cache entry
from issuing another remove?
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail:
[EMAIL PROTECTED]
For additional commands, e-mail:
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
