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

Evgeny Stanilovsky updated IGNITE-24476:
----------------------------------------
    Description: 
Need to handle event introduced in [1].

CPCC should not have an impact on RW transactions execution. It is proposed to 
do like:

Initiate new affinity replicator (new zone with new affinity) 
After [1], get catalog activation time (time T1).
Affinity replicator need to replicate all tx`s with beginTs >= T1

Definition of done: messages are routed into both new and old zones.
Main candidate for splitting 
org.apache.ignite.internal.table.distributed.storage.InternalTableImpl#enlistInTx
Seems enlistInTx implementations need to be implemented in separate class, 
which listen event from [1]
Listen cpcc task cancellation event (seems additional is needed) and cancel 
cpcc related activity.

[1] https://issues.apache.org/jira/browse/IGNITE-24442

  was:
Need to handle event introduced in [1].



Definition of done: messages are routed into both new and old zones.
Main candidate for splitting 
org.apache.ignite.internal.table.distributed.storage.InternalTableImpl#enlistInTx
Seems enlistInTx implementations need to be implemented in separate class, 
which listen event from [1]
Listen cpcc task cancellation event (seems additional is needed) and cancel 
cpcc related activity.

[1] https://issues.apache.org/jira/browse/IGNITE-24442


> CPCC. Provide implementation for new affinity replication switch
> ----------------------------------------------------------------
>
>                 Key: IGNITE-24476
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24476
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>    Affects Versions: 3.0
>            Reporter: Evgeny Stanilovsky
>            Priority: Major
>              Labels: ignite-3
>
> Need to handle event introduced in [1].
> CPCC should not have an impact on RW transactions execution. It is proposed 
> to do like:
> Initiate new affinity replicator (new zone with new affinity) 
> After [1], get catalog activation time (time T1).
> Affinity replicator need to replicate all tx`s with beginTs >= T1
> Definition of done: messages are routed into both new and old zones.
> Main candidate for splitting 
> org.apache.ignite.internal.table.distributed.storage.InternalTableImpl#enlistInTx
> Seems enlistInTx implementations need to be implemented in separate class, 
> which listen event from [1]
> Listen cpcc task cancellation event (seems additional is needed) and cancel 
> cpcc related activity.
> [1] https://issues.apache.org/jira/browse/IGNITE-24442



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

Reply via email to