You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2018/10/02 09:50:00 UTC

[jira] [Commented] (IGNITE-8006) Starting multiple caches slows down exchange process on joining node

    [ https://issues.apache.org/jira/browse/IGNITE-8006?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16635226#comment-16635226 ] 

Ignite TC Bot commented on IGNITE-8006:
---------------------------------------

{panel:title=No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity Run All|http://ci.ignite.apache.org/viewLog.html?buildId=1980148&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Starting multiple caches slows down exchange process on joining node
> --------------------------------------------------------------------
>
>                 Key: IGNITE-8006
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8006
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Assignee: Anton Kalashnikov
>            Priority: Major
>             Fix For: 2.8
>
>
> In some cases when we starts multiple caches (over 2K caches), we can get a stop on exchange when new node joining to the cluster.
> Coordinator-node wait to receive a single message from all other nodes, but last node (which want to joining to the cluster) stopped on starting caches:
>  
> {noformat}
> Stack trace
>  at java.lang.Thread.dumpStack(Thread.java:1329)
>  at org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1159)
>  at org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1900)
>  at org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:1764)
>  at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:740)
>  at org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:622)
>  at org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2329)
>  at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
>  at java.lang.Thread.run(Thread.java:745)
> {noformat}
> It blocks cluster exchange process until all caches started on the last node.
> We should start caches in parallel threads or exclude the action from exchange init process.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)