[ https://issues.apache.org/jira/browse/IGNITE-10228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16686167#comment-16686167 ]
Ignite TC Bot commented on IGNITE-10228: ---------------------------------------- {panel:title=No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel} [TeamCity Run All Results|http://ci.ignite.apache.org/viewLog.html?buildId=2314457&buildTypeId=IgniteTests24Java8_InspectionsCore] > 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)