[
https://issues.apache.org/jira/browse/IGNITE-8295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16440725#comment-16440725
]
ASF GitHub Bot commented on IGNITE-8295:
----------------------------------------
GitHub user AMashenkov opened a pull request:
https://github.com/apache/ignite/pull/3842
IGNITE-8295: Fixed wrong checkpointLock vs partStoreLock order.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8295
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/3842.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 #3842
----
commit fb7956b0c4fc9d8b62aac1f831e0c0ef939275da
Author: Andrey V. Mashenkov <andrey.mashenkov@...>
Date: 2018-04-17T10:32:12Z
Fixed wrong checkpointLock vs partStoreLock order.
----
> Possible deadlock on partition eviction.
> ----------------------------------------
>
> Key: IGNITE-8295
> URL: https://issues.apache.org/jira/browse/IGNITE-8295
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Reporter: Andrew Mashenkov
> Assignee: Andrew Mashenkov
> Priority: Major
> Fix For: 2.6
>
> Attachments: deadlock.stack
>
>
> GridCacheOffheapManager.recreateCacheDataStore() calls
> updatePartitionCounter() under partStoreLock which may try to acquire
> checkpointReadLock.
> recreateCacheDataStore() method can be called with checkpointReadLock (on
> GridDhtPartitionsExchangeFuture.updatePartitionFullMap)
> or without checkpointReadLock (GridDhtPartitionEvictor thread calls
> evictPartitionAsync),
> So, checkpoint can cause a deadlock if it happens in between.
> Seems, we should acquire checkpointReadLock before partStoreLock.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
