ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ignite TC Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-8006) Starting multiple caches slows down exchange process on joining node
Date Thu, 18 Oct 2018 06:52:00 GMT

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

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

{panel:title=Possible Blockers|borderStyle=dashed|borderColor=#ccc|titleBGColor=#F7D6C1}
{color:#d04437}Hadoop{color} [[tests 0 TIMEOUT , Exit Code |https://ci.ignite.apache.org/viewLog.html?buildId=2105249]]
* IgniteHadoopFileSystemClientBasedPrimarySelfTest.testClientReconnect (last started)

{panel}
[TeamCity Run All|http://ci.ignite.apache.org/viewLog.html?buildId=2105333&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)

Mime
View raw message