Vladislav Pyatkov created IGNITE-8006: -----------------------------------------
Summary: Starting multiple caches inhibits 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 In some cases when we starts multiple caches (over 2K caches), we can to got 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} that inhibits cluster exchange process, until all caches started on the last node. We should to start caches in parallel threads or exclude the action from exchange init process. -- This message was sent by Atlassian JIRA (v7.6.3#76005)