[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

[Dan Berindei (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dan Berindei updated ISPN-1012:
-------------------------------

              Status: Pull Request Sent  (was: Reopened)
    Git Pull Request: https://github.com/infinispan/infinispan/pull/391


    * (In the ISPN-1171 commit) I modified ConfigurationValidatingVisitor to disable L1OnRehash when L1 is disabled.
    * I modified DefaultCacheManager to apply the validating visitor in all the constructors for the global configuration and when creating the cache for the named cache configurations.
    * I fixed CloneableConfigurationComponent so cloned configuration objects don't share the overridden elements list.
    * In the ISPN-1171 commit I modified ConfigurationValidatingVisitor to disable L1OnRehash when L1 is disabled.
    * I modified DefaultCacheManager to apply the validating visitor in all the constructors for the global configuration and when creating the cache for the named cache configurations.
    * I fixed CloneableConfigurationComponent so cloned configuration objects don't share the overridden elements list.


> 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: Dan Berindei
>            Priority: Critical
>             Fix For: 5.0.0.CR7, 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