You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (JIRA)" <ji...@apache.org> on 2019/01/01 15:01:00 UTC

[jira] [Commented] (IGNITE-5003) Parallel write&evict same key in CacheWriteBehindStore

    [ https://issues.apache.org/jira/browse/IGNITE-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16731610#comment-16731610 ] 

Vyacheslav Koptilin commented on IGNITE-5003:
---------------------------------------------

Hello [~aealeksandrov] ,

The changes look good to me.

> Parallel write&evict same key in CacheWriteBehindStore
> ------------------------------------------------------
>
>                 Key: IGNITE-5003
>                 URL: https://issues.apache.org/jira/browse/IGNITE-5003
>             Project: Ignite
>          Issue Type: Improvement
>    Affects Versions: 1.9
>            Reporter: Alexander Belyak
>            Assignee: Andrey Aleksandrov
>            Priority: Major
>             Fix For: 2.8
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Now GridCacheWriteBehindStore.updateCache wait for writeLock in StatefulValue and, moreover, waitForFlush() if value is in pending (flushing) state. 
> We need to remove waiting.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)