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

[Ignite TC Bot (JIRA)]

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

Ignite TC Bot commented on IGNITE-5003:
---------------------------------------

{panel:title=--> Run :: All: Possible 
Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Cache 3{color} [[tests 
3|https://ci.ignite.apache.org/viewLog.html?buildId=2546319]]
* IgniteBinaryObjectsCacheTestSuite3: 
GridCacheWriteBehindStoreMultithreadedSelfTest.testPutGetRemoveWithCoalescing - 
0,0% fails in last 416 master runs.
* IgniteBinaryObjectsCacheTestSuite3: 
GridCacheWriteBehindStoreMultithreadedSelfTest.testStoreFailureWithCoalescing - 
0,0% fails in last 416 master runs.

{color:#d04437}_Licenses Headers_{color} [[tests 0 Exit Code 
|https://ci.ignite.apache.org/viewLog.html?buildId=2546320]]

{panel}
[TeamCity *--> Run :: All* 
Results|https://ci.ignite.apache.org/viewLog.html?buildId=2540655&buildTypeId=IgniteTests24Java8_RunAll]

> 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
>
> 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)