You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/09/13 16: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=16613763#comment-16613763 ]
ASF GitHub Bot commented on IGNITE-8006:
----------------------------------------
GitHub user akalash opened a pull request:
https://github.com/apache/ignite/pull/4752
IGNITE-8006 added parallel start of caches.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8006
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4752.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4752
----
commit a457c8b4c23be57cea11f7f7a49c5bc695adde9d
Author: Anton Kalashnikov <ka...@...>
Date: 2018-09-13T16:44:40Z
IGNITE-8006 added parallel start of caches.
----
> 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: Alexey Stelmak
> Priority: Major
>
> 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)