You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Alexey Goncharuk (JIRA)" <ji...@apache.org> on 2018/10/27 13:22:00 UTC

[jira] [Updated] (IGNITE-9682) Update full partition map in parallel

     [ https://issues.apache.org/jira/browse/IGNITE-9682?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Goncharuk updated IGNITE-9682:
-------------------------------------
    Ignite Flags:   (was: Docs Required)

> Update full partition map in parallel
> -------------------------------------
>
>                 Key: IGNITE-9682
>                 URL: https://issues.apache.org/jira/browse/IGNITE-9682
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Oleg Ostanin
>            Assignee: Oleg Ostanin
>            Priority: Major
>
> I've noticed that we are updating full partition map for each cache sequentially and during such update we are unable to run much of other tasks. Hence there should be some free threads which we can use for parallel updating. Sometimes it takes 20-30 seconds to update a map for 100+ caches before rebalancing can even start:
> {noformat}
> [2018-09-24 16:38:49,016][INFO ][sys-#219|#219] Received full message, will finish exchange [node=4d6b5921-0a61-4bfa-bf11-b8a1b8332dce, resVer=AffinityTopologyVersion [topVer=19, minorTopVer=2]]
> ...
> [2018-09-24 16:39:01,217][INFO ][sys-#219|#219] Finish exchange future [startVer=AffinityTopologyVersion [topVer=19, minorTopVer=2], resVer=AffinityTopologyVersion [topVer=19, minorTopVer=2], err=null]
> {noformat}



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