[infinispan-issues] [JBoss JIRA] Updated: (ISPN-1012) With L1 disabled a new node join may result some entries are not invalidated for non-owner in DIST mode
Manik Surtani (JIRA)
jira-events at lists.jboss.org
Mon Jun 6 07:38:00 EDT 2011
[ https://issues.jboss.org/browse/ISPN-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Manik Surtani updated ISPN-1012:
--------------------------------
Fix Version/s: 5.0.0.CR5
5.0.0.FINAL
Priority: Critical (was: Major)
> With L1 disabled a new node join may result some entries are not invalidated for non-owner in DIST mode
> -------------------------------------------------------------------------------------------------------
>
> Key: ISPN-1012
> URL: https://issues.jboss.org/browse/ISPN-1012
> Project: Infinispan
> Issue Type: Bug
> Components: Distributed Cache
> Affects Versions: 4.2.1.FINAL
> Reporter: Changgeng Li
> Assignee: Manik Surtani
> Priority: Critical
> Fix For: 5.0.0.CR5, 5.0.0.FINAL
>
> Attachments: DataCountTest.java, test-4.2.1final.tgz, test-4.2.1final.zip, test-4.2.1final.zip, test-5.0.0.CR3.zip
>
>
> I have a test case that have 30,000 entries in cache in dist mode with number of owner set to 2 and L1 is disabled. A new node join the cluster, then the total number of entries in all cache is larger than 60,000. Even worse, after I execute cache.clear() on all caches in the cluster, there are still lots of entries left.
> The attached unit test can reproduce this issue.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the infinispan-issues
mailing list