[
https://issues.apache.org/jira/browse/IGNITE-22956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Gusakov updated IGNITE-22956:
------------------------------------
Description:
*Motivation*
See https://issues.apache.org/jira/browse/IGNITE-22689
*Definition of done*
- On the table create all table partition listeners loaded to the local zone
replica (if exsists).
- On the zone replica start all table partition listeners loaded to the new
zone replica
*Implementation note*
- When the TableManager received the
PartitionReplicaLifecycleEvent.AFTER_REPLICA_STARTED event it must use the
current state (not the catalog one) to collect the partition listeners, which
must be created and loaded to the zone replica/
- When the TableManager received the table create event from catalog - it must
check the current replica list in the PartitionReplicaLifecycleManager and
loaded new partitoin listeners if needed.
- The two previous steps must work correctly together at the same time, because
there are now synchronization mechanism between the local events and catalog
events.
was:
*Motivation*
See https://issues.apache.org/jira/browse/IGNITE-22689
*Definition of done*
- On the table create all table partition listeners loaded to the local zone
replica (if exsists).
- On the zone replica start all table partition listeners loaded to the new
zone replica
*Implementation details*
> Implement the local event driven table processors creation
> ------------------------------------------------------------
>
> Key: IGNITE-22956
> URL: https://issues.apache.org/jira/browse/IGNITE-22956
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Gusakov
> Assignee: Kirill Gusakov
> Priority: Major
> Labels: ignite-3
>
> *Motivation*
> See https://issues.apache.org/jira/browse/IGNITE-22689
> *Definition of done*
> - On the table create all table partition listeners loaded to the local zone
> replica (if exsists).
> - On the zone replica start all table partition listeners loaded to the new
> zone replica
> *Implementation note*
> - When the TableManager received the
> PartitionReplicaLifecycleEvent.AFTER_REPLICA_STARTED event it must use the
> current state (not the catalog one) to collect the partition listeners, which
> must be created and loaded to the zone replica/
> - When the TableManager received the table create event from catalog - it
> must check the current replica list in the PartitionReplicaLifecycleManager
> and loaded new partitoin listeners if needed.
> - The two previous steps must work correctly together at the same time,
> because there are now synchronization mechanism between the local events and
> catalog events.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
