[infinispan-issues] [JBoss JIRA] (ISPN-5575) Shared write-behind store can read stale entries on joiner

[Dan Berindei (JIRA)]

    [ https://issues.jboss.org/browse/ISPN-5575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083539#comment-13083539 ] 

Dan Berindei commented on ISPN-5575:
------------------------------------

It doesn't matter if the shared store is configured with {{shared="true"}} or with {{singleton="true"}}. Both options will allow a joiner to read keys that it doesn't have in memory directly from the store, after state transfer is over, and state transfer can finish before AsyncCacheWriter writes all the modifications to the store.

> Shared write-behind store can read stale entries on joiner
> ----------------------------------------------------------
>
>                 Key: ISPN-5575
>                 URL: https://issues.jboss.org/browse/ISPN-5575
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core, Loaders and Stores
>    Affects Versions: 8.0.0.Alpha2, 7.2.3.Final
>            Reporter: Dan Berindei
>            Assignee: Dan Berindei
>             Fix For: 8.0.0.Final
>
>
> The AsyncCacheWriter modification queue is not sent with state transfer when the store is shared. A joiner can then read from the shared store a stale version of entries that have updates in the modification queue but are no longer in memory (because they were either removed explicitly, or evicted). 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)