[
https://issues.apache.org/jira/browse/IGNITE-21805?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Gusakov updated IGNITE-21805:
------------------------------------
Description:
*Motivation*
At the moment we have some places inside the TableManager, which:
* Use RaftManager to start/stop RAFT nodes
* Use RAFT clients for some rebalance activities
This fact prevents us on the track of zone-based collocation. The further
collocation steps will be easier, if we will move the whole RAFT connected
operation to the Replica class. Moreover, it should be there semantically
*Definition of done*
RAFT communication hidden under the Replica abstraction.
was:
*Motivation*
At the moment we have some places inside the TableManager, which:
* Use RaftManager to start/stop RAFT nodes
* Use RAFT clients for some rebalance activities
This fact prevents us on the track of zone-based collocation. The further
collocation steps will be easier, if we will move the whole RAFT connected
operation to the Replica class. Moreover, it should be there semantically
> Refactor TableManager and move all RAFT related pieces to Replica
> -----------------------------------------------------------------
>
> Key: IGNITE-21805
> URL: https://issues.apache.org/jira/browse/IGNITE-21805
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Gusakov
> Priority: Major
>
> *Motivation*
> At the moment we have some places inside the TableManager, which:
> * Use RaftManager to start/stop RAFT nodes
> * Use RAFT clients for some rebalance activities
> This fact prevents us on the track of zone-based collocation. The further
> collocation steps will be easier, if we will move the whole RAFT connected
> operation to the Replica class. Moreover, it should be there semantically
> *Definition of done*
> RAFT communication hidden under the Replica abstraction.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
