[
https://issues.apache.org/jira/browse/IGNITE-20362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vyacheslav Koptilin updated IGNITE-20362:
-----------------------------------------
Labels: ignite-3 (was: )
> Implement the ReplicationServerManager component
> ------------------------------------------------
>
> Key: IGNITE-20362
> URL: https://issues.apache.org/jira/browse/IGNITE-20362
> Project: Ignite
> Issue Type: Task
> Reporter: Kirill Gusakov
> Priority: Major
> Labels: ignite-3
>
> *Motivation*
> Under the design
> [document|https://github.com/apache/ignite-3/blob/1abb67c8770179d5d3e295876b73893f3845a08e/modules/distribution-zones/tech-notes/zone-collocation.md#L1]
> was introduced new component, which must decouple the intention to start new
> zone partition peer and intention to populate it by concrete table partition
> listeners.
> *Definition of done*
> - The right name for this component chosen ( :) )
> - Component is implemented with appropriate start/stop behaviour:
> -- if component is not started
> addReplicationServer/addTablePartitionListener just populate the internal
> state machine with the appropriate intentions
> -- on the start of the component all intentions must be resolved in real
> peers with aggregated state machines
> -- after the start addReplicationServer/addTablePartitionListener methods
> must immediately start the needed entities
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
