ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IGNITE-1837) Rebalancing on a big cluster (30 nodes and more)
Date Tue, 21 Feb 2017 11:39:44 GMT

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

Semen Boikov resolved IGNITE-1837.
    Resolution: Won't Fix
      Assignee:     (was: Semen Boikov)

There were implemented several optimizations in discovery, affinity calculation and exchange
processing (e.g. IGNITE-4296), after this suggested optimization does not make sense.

> Rebalancing on a big cluster (30 nodes and more)
> ------------------------------------------------
>                 Key: IGNITE-1837
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1837
>             Project: Ignite
>          Issue Type: Bug
>          Components: general
>    Affects Versions: ignite-1.4
>            Reporter: Denis Magda
> It seems that Ignite has different rebalancing related issues that appear when a big
cluster is started.
> Under the big cluster I mean:
> - cluster of 64 server nodes;
> - cluster of 64 server and 64 client nodes.
> The issues can be divided on three main use cases.
> 1) Slow rebalancing on start.
> - If to set partitions number for some cache to value bigger than default one (to 3200
or to 6400, etc.) then rebalancing of such caches may take several minutes. The caches are
empty at that time. In addition, as a part of this issue let's document that the number of
partitions can't exceed some value.
> - exchange message on NODE_JOINED event that times out for a long time. Discussed there:
> 2) Slow rebalancing on client nodes shutdown.
> If to stop a significant number of client nodes at the same time then again by some reason
the rebalancing will take serveral minutes.

This message was sent by Atlassian JIRA

View raw message