[
https://issues.apache.org/jira/browse/IGNITE-24220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander Lapin updated IGNITE-24220:
-------------------------------------
Description:
h3. Motivation
The collocation epic will be implemented by a working group unfamiliar with the
already written code base. Thus, it makes sense to familiarize yourself with
current solutions and compile a list of refactoring proposals.
As entry points I'd suggest to start with PartitionReplicaLifecycleManager that
manager zone's replicas along with LocalPartitionReplicaEvent processing on the
TableManager side. Please pay special attention to the mechanism that ensures
that there are no races in the processing of the table creation event and the
creation of zone replicas.
h3. Definition of Done
* The result is a list of suggested refactorings.
> Technical audit of the collocation code base
> --------------------------------------------
>
> Key: IGNITE-24220
> URL: https://issues.apache.org/jira/browse/IGNITE-24220
> Project: Ignite
> Issue Type: Task
> Reporter: Alexander Lapin
> Priority: Major
> Labels: ignite-3
>
> h3. Motivation
> The collocation epic will be implemented by a working group unfamiliar with
> the already written code base. Thus, it makes sense to familiarize yourself
> with current solutions and compile a list of refactoring proposals.
> As entry points I'd suggest to start with PartitionReplicaLifecycleManager
> that manager zone's replicas along with LocalPartitionReplicaEvent processing
> on the TableManager side. Please pay special attention to the mechanism that
> ensures that there are no races in the processing of the table creation event
> and the creation of zone replicas.
> h3. Definition of Done
> * The result is a list of suggested refactorings.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
