You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Voronkin (JIRA)" <ji...@apache.org> on 2018/11/13 07:34:00 UTC
[jira] [Assigned] (IGNITE-10228) Start multiple caches in parallel
may lead to the fact that some of the caches won't be registered.
[ https://issues.apache.org/jira/browse/IGNITE-10228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Voronkin reassigned IGNITE-10228:
---------------------------------------
Assignee: Pavel Voronkin
> Start multiple caches in parallel may lead to the fact that some of the caches won't be registered.
> ---------------------------------------------------------------------------------------------------
>
> Key: IGNITE-10228
> URL: https://issues.apache.org/jira/browse/IGNITE-10228
> Project: Ignite
> Issue Type: Bug
> Components: cache
> Affects Versions: 2.6
> Reporter: Vyacheslav Koptilin
> Assignee: Pavel Voronkin
> Priority: Major
> Attachments: CacheStartingParallelTest.java
>
>
> It looks like the root cause of the issue is that {{CacheGroupContext.addCacheContext()}} (which is called in parallel) does not use a lock/semaphore in order to synchronize {{caches}} updates.
>
> {code:java}
> private void addCacheContext(GridCacheContext cctx) {
> ArrayList<GridCacheContext> caches = new ArrayList<>(this.caches);
> boolean add = caches.add(cctx);
> ...
> this.caches = caches;
> }
> {code}
>
> The possible workaround is to disable parallel start of caches by setting the {{IGNITE_ALLOW_START_CACHES_IN_PARALLEL}} property to {{false}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)