[
https://issues.apache.org/jira/browse/IGNITE-9389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16593893#comment-16593893
]
ASF GitHub Bot commented on IGNITE-9389:
----------------------------------------
GitHub user dmekhanikov opened a pull request:
https://github.com/apache/ignite/pull/4626
IGNITE-9389 Avoid deadlocks on cache#close()
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-9389
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4626.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 #4626
----
commit 18bf109f386ea87470f9371faeafd7e2104e09b4
Author: Denis Mekhanikov <dmekhanikov@...>
Date: 2018-08-27T16:13:57Z
IGNITE-9389 Add test.
commit 3321f77bd7242ec0a26002bee152bf6522943586
Author: Denis Mekhanikov <dmekhanikov@...>
Date: 2018-08-27T16:16:16Z
IGNITE-9389 Avoid deadlock on cache#close().
----
> Concurrent Cache#close and put/get operations lead to a deadlock
> ----------------------------------------------------------------
>
> Key: IGNITE-9389
> URL: https://issues.apache.org/jira/browse/IGNITE-9389
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.6
> Reporter: Denis Mekhanikov
> Assignee: Denis Mekhanikov
> Priority: Major
> Attachments: CacheConcurrentUseAndCloseTest.java
>
>
> When cache is closed on a client node, while it is being used concurrently in
> other threads, deadlock may occur.
> Test case, reproducing the problem is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
