You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mirza Aliev (Jira)" <ji...@apache.org> on 2025/01/29 08:04:00 UTC

[jira] [Updated] (IGNITE-24331) Support DisasterRecoveryManager#localPartitionStates and globalPartitionStates in Collocation track

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

Mirza Aliev updated IGNITE-24331:
---------------------------------
    Summary: Support DisasterRecoveryManager#localPartitionStates and globalPartitionStates in Collocation track  (was: Support DisasterRecoveryManager#localPartitionStates and globalPartitionStates in Colocation track)

> Support DisasterRecoveryManager#localPartitionStates and globalPartitionStates in Collocation track
> ---------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-24331
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24331
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Mirza Aliev
>            Priority: Major
>              Labels: ignite-3
>
> h3. Motivation
> This ticket is a part of the implementation track for https://issues.apache.org/jira/browse/IGNITE-24330, where we have revised DisasterRecoveryManager API in alignment with Colocation track
> In this ticket we have to provide a correct behaviour for {{DisasterRecoveryManager#localPartitionStates}} and close method {{DisasterRecoveryManager#globalPartitionStates}} which uses {{localPartitionStates}}.
> Currently, those methods return a mapping of {{TablePartitionId}} to the mapping between a node name and a partition state. 
> To conform Collocation track, those methods must use {{ZonePartitionId}} and hence return states of a zone's partition rather than table's.



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