You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Semen Boikov (JIRA)" <ji...@apache.org> on 2017/07/17 09:32:00 UTC
[jira] [Created] (IGNITE-5763) Race in concurrent client cache
start
Semen Boikov created IGNITE-5763:
------------------------------------
Summary: Race in concurrent client cache start
Key: IGNITE-5763
URL: https://issues.apache.org/jira/browse/IGNITE-5763
Project: Ignite
Issue Type: Bug
Components: cache
Reporter: Semen Boikov
Assignee: Semen Boikov
Priority: Critical
Fix For: 2.2
Issue was introduced as part of IGNITE-5272, this race is possible:
- two threads on client call getOrCreateCache(s)
- one of threads initiates cache start and sends custom event, this event is processed in discovery thread but is not passed yet to DiscoveryWorker
- second thread sees that cache descriptor already exists and adds 'client cache start' event in DiscoveryWorker before cache start event is added in DiscoveryWorker
- when 'client cache start' event processed, cache does not exists and getOrCreateCache(s) fails
Added test IgniteDynamicCacheMultinodeTest.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)