You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Kirill Gusakov (Jira)" <ji...@apache.org> on 2023/01/25 11:54:00 UTC

[jira] [Resolved] (IGNITE-18286) Design the protocol for exacltly once processing of rebalance triggers per scope

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

Kirill Gusakov resolved IGNITE-18286.
-------------------------------------
    Resolution: Invalid

Not valid anymore, see https://issues.apache.org/jira/browse/IGNITE-18634

> Design the protocol for exacltly once processing of rebalance triggers per scope
> --------------------------------------------------------------------------------
>
>                 Key: IGNITE-18286
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18286
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Kirill Gusakov
>            Assignee: Kirill Gusakov
>            Priority: Major
>              Labels: ignite-3
>
> Rebalance process can has causes with different nature:
>  * Table reconfiguration
>  * Node outage
>  * Manual triggers or triggers based on workloads
> For the first one we has a revision, which can help to process it exactly once cluster-wide. But it isn't true for others. We must find a way to schedule the rebalance process by different types of events.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)