[
https://issues.apache.org/jira/browse/IGNITE-12365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971411#comment-16971411
]
Ilya Kasnacheev commented on IGNITE-12365:
------------------------------------------
I have attached a test. testTreeSetRemoveAll would not fail (expected),
testHashSetRemoveAll will deadlock (expected-ish), testRemoveAll will deadlock
too (totally mad).
> Concurrent removeAll() on the same cache leads to deadlock
> ----------------------------------------------------------
>
> Key: IGNITE-12365
> URL: https://issues.apache.org/jira/browse/IGNITE-12365
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.8
> Reporter: Ilya Kasnacheev
> Priority: Critical
> Labels: stupid
> Attachments: RemoveAllDeadlockTest.java, removeAll-deadlock.txt
>
>
> That's because removeAll is implemented as invokeAll with HashSet parameter.
> invokeAll + HashSet = 💀
> I will attach simple reproducer (please note that multiple invocations of
> test is needed, typically 5-10) as well as thread dumps.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
