[
https://issues.apache.org/jira/browse/IGNITE-5003?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16720285#comment-16720285
]
ASF GitHub Bot commented on IGNITE-5003:
----------------------------------------
GitHub user aealeksandrov opened a pull request:
https://github.com/apache/ignite/pull/5664
IGNITE-5003: Hanging of parallel write&evict for the same key in Cach…
…eWriteBehindStore fixed.
Now GridCacheWriteBehindStore.updateCache wait for writeLock in
StatefulValue and, moreover, waitForFlush() if value is in pending (flushing)
state. We need to remove waiting.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-5003
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/5664.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #5664
----
commit 759fbb5e271d86583087b897e3659d86bd41a125
Author: Andrei Aleksandrov <aealexsandrov@...>
Date: 2018-12-13T15:16:17Z
IGNITE-5003: Hanging of parallel write&evict for the same key in
CacheWriteBehindStore fixed.
----
> 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)
