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

Mirza Aliev updated IGNITE-24335:
---------------------------------
    Summary: Support DisasterRecoveryManager#restartPartition in Colocation 
track  (was: Support DisasterRecoveryManager#restartPartition in Collocation 
track)

> Support DisasterRecoveryManager#restartPartition in Colocation track
> --------------------------------------------------------------------
>
>                 Key: IGNITE-24335
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24335
>             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 Collocation track
> In this ticket we have to provide a correct behaviour for 
> {{DisasterRecoveryManager#restartPartition}} for partitions from zones.
> h3. Implementation notes
> As usual for the such methods from DisasterRecoveryManager, we must switch to 
> {{ZonePartitionId}}. Also this mechanism uses under the hood 
> {{TableManager#restartPartition}}. Seems that we need to have similar method 
> in {{PartitionReplicaLifecycleManager}}, which has all prerequisites like  
> {{PartitionReplicaLifecycleManager#weakStopPartition}}, 
> {{PartitionReplicaLifecycleManager#waitForMetadataCompleteness}}
> h3. Definition of Done
> * DisasterRecoveryManager API is enriched with {{restartPartition}} method 
> that works with zones' based partitions



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

Reply via email to