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

Mirza Aliev updated IGNITE-24331:
---------------------------------
    Description: 
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.

h3. Definition of Done 

* DisasterRecoveryManager API is enriched with {{localPartitionStates}} and 
{{globalPartitionStates}} methods that work with zones' based partitions  

  was:
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.

h3. Definition of Done 

* DisasterRecoveryManager API is enriched with {{localPartitionStates}} and 
{{globalPartitionStates}} methods that are work with zones' based partitions  


> 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.
> h3. Definition of Done 
> * DisasterRecoveryManager API is enriched with {{localPartitionStates}} and 
> {{globalPartitionStates}} methods that work with zones' based partitions  



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

Reply via email to