-
1. Re: Keys not being invalidated on older node when new node joins
gupabhi Nov 11, 2010 10:20 AM (in response to gupabhi)To add to the above, I've done some further testing that proves there is a problem. I set ignoreModifications="true" for the loader on node A.
Once node A loads all the data from the fileStore I start node B. Node B get 'n' entries from Node A. I modify one of the 'n' entries in node 'B'. Then I print the values of all the entries in node 'A'. Node 'A' does not see this change as suspected above.
Further, if an entry that is not local to 'B' is updated, then the change is reflected in A.
I would really appreciate a comment on this issue?
Thanks,
Abhi
-
2. Re: Keys not being invalidated on older node when new node joins
galder.zamarreno Nov 16, 2010 6:12 AM (in response to gupabhi)Wrt the first comment, that looks like a bug. Could you try with latest 4.2.0.BETA1 to see if the issue is still present? If still present, please open a JIRA in https://jira.jboss.org/browse/ISPN so that we can investigate it.
Wrt the 2nd comment, note that retrieving all entries, when doing so against a distributed cache, it only brings the entries that are local to the cache. It does not attempt to bring anything from B. So, it's prob right that you don't see the change. If the entry is not local to B, it's logical that the update is present in A, cos the entry is local to it and hence it should have been updated.
The only thing that looks odd here is that A has an entry that belongs to B when L1 is disabled and numOwners=1.