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 Tkalenko (Jira)" <ji...@apache.org> on 2022/10/31 12:14:00 UTC

[jira] [Updated] (IGNITE-18030) Integration of the new full rebalance API with IncomingSnapshotCopier

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

Kirill Tkalenko updated IGNITE-18030:
-------------------------------------
    Description: 
We need to integrate the new full rebalance API without losing user data with *IncomingSnapshotCopier*, additional tests may be needed.

The main idea is described in IGNITE-17990.

API should be in ticket IGNITE-18021 and IGNITE-18022.

  was:
We need to integrate the new full rebalance API without losing user data with *IncomingSnapshotCopier*, additional tests may be needed.

The main idea is described in IGNITE-17990.


> Integration of the new full rebalance API with IncomingSnapshotCopier
> ---------------------------------------------------------------------
>
>                 Key: IGNITE-18030
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18030
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> We need to integrate the new full rebalance API without losing user data with *IncomingSnapshotCopier*, additional tests may be needed.
> The main idea is described in IGNITE-17990.
> API should be in ticket IGNITE-18021 and IGNITE-18022.



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