[infinispan-issues] [JBoss JIRA] Resolved: (ISPN-681) Some of Lucene's readlocks are persisted to the CacheStore

[Sanne Grinovero (JIRA)]

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

Sanne Grinovero resolved ISPN-681.
----------------------------------

    Resolution: Won't Fix


For any cache having a CacheStore enabled it's possible that contained data is pushed to the store, even if it was put in the cache using the Flag.SKIP_CACHE_STORE, as values might be re-written during rehashing.

ReadLocks of the Lucene Directory are ignored when written in the store, so even in case they are written they are harmless.

To really avoid having readlock instances in the store it's recommended to use the features provided by ISPN-616 to configure a cache for the locks only, having no cache store enabled, so this problem is not relevant anymore.

> Some of Lucene's readlocks are persisted to the CacheStore
> ----------------------------------------------------------
>
>                 Key: ISPN-681
>                 URL: https://jira.jboss.org/browse/ISPN-681
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Lucene Directory
>    Affects Versions: 4.1.0.Final, 4.2.0.ALPHA2
>            Reporter: Sanne Grinovero
>            Assignee: Sanne Grinovero
>             Fix For: 4.2.0.BETA1, 4.2.0.Final
>
>
> After some days of load testing I can find keys like "_3w.cfs|RL|comments" in the CacheStore (using jdbc store), while it should be guaranteed that they are never stored.
> This is also introducing high contention on MySQL, generating errors under load, as the readlocks are frequent and shortlived.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira