[infinispan-issues] [JBoss JIRA] Resolved: (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)]

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

Manik Surtani resolved ISPN-1012.
---------------------------------

    Fix Version/s:     (was: 4.2.2.BETA1)
       Resolution: Cannot Reproduce Bug


A couple of things here:

* Your test (DataCountTest) did not disable L1.  After disabling L1, I don't see the "extra" entries.
* The clear() commands sometimes get issued before a rehash completes, which is why some transient state being moved across gets applied after the clear().  

I've updated the test a bit, and it is now here:  https://gist.github.com/936439

> 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
>         Attachments: DataCountTest.java, test-4.2.1final.tgz, test-4.2.1final.zip, test-4.2.1final.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