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/12/27 14:28:00 UTC

[jira] [Updated] (IGNITE-18029) Implementation of a full rebalance for PersistentPageMemoryMvPartitionStorage on receiver

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

Kirill Tkalenko updated IGNITE-18029:
-------------------------------------
    Summary: Implementation of a full rebalance for PersistentPageMemoryMvPartitionStorage on receiver  (was: Implementation of a full rebalance without loss of user data for PersistentPageMemoryMvPartitionStorage on receiver)

> Implementation of a full rebalance for PersistentPageMemoryMvPartitionStorage on receiver
> -----------------------------------------------------------------------------------------
>
>                 Key: IGNITE-18029
>                 URL: https://issues.apache.org/jira/browse/IGNITE-18029
>             Project: Ignite
>          Issue Type: Task
>            Reporter: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> We need to implement the API from IGNITE-18073 for *PersistentPageMemoryMvPartitionStorage*, enable the disabled test.
> And also add a check that if we restart the storage for which we have not finished rebalancing, then the storage will be reset.
> The main idea is described in IGNITE-17990.



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