[
https://issues.apache.org/jira/browse/IGNITE-24354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17927769#comment-17927769
]
Alexander Lapin commented on IGNITE-24354:
------------------------------------------
PR will be merged later, on colocation finish steps in order not to mix fancy
changePeers-through-primary and colocation.
> Move ChangePeersAndLearnersAsyncReplicaRequest processing to
> ZonePartitionReplicaListener
> -----------------------------------------------------------------------------------------
>
> Key: IGNITE-24354
> URL: https://issues.apache.org/jira/browse/IGNITE-24354
> Project: Ignite
> Issue Type: Task
> Reporter: Alexander Lapin
> Assignee: Mikhail Efremov
> Priority: Major
> Labels: ignite-3
> Time Spent: 20m
> Remaining Estimate: 0h
>
> h3. Motivation
> Within colocation track we should reasonably move table-not-specific requests
> and commands processing from PartitionReplicaListener and PartitionListener
> to ZonePartitionReplicaListener and ZonePartitionRaftListener.
> ChangePeersAndLearnersAsyncReplicaRequest is one of such requests to be moved.
> h3. Definition of Done
> * It’s possible to rebalance zone partition from one set of nodes to another.
> h3. Implementation Notes
> * Copy PartitionReplicaListener#processChangePeersAndLearnersReplicaRequest
> along with corresponding trigger to ZonePartitionRaftListener.
> * Hide original
> PartitionReplicaListener#processChangePeersAndLearnersReplicaRequest under
> colocation feature flag.
> * Add corresponding test or adjust
> testTableReplicaListenersCreationAfterRebalance and
> testTableReplicaListenersRemoveAfterRebalance.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)