[
https://issues.apache.org/jira/browse/IGNITE-21252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kirill Gusakov updated IGNITE-21252:
------------------------------------
Summary: Partition RAFT client must use pending and stable assignments as a
list of peers during the rebalance (was: Partition RAFT client must use
pending and stable assignments as list of peers)
> Partition RAFT client must use pending and stable assignments as a list of
> peers during the rebalance
> -----------------------------------------------------------------------------------------------------
>
> Key: IGNITE-21252
> URL: https://issues.apache.org/jira/browse/IGNITE-21252
> Project: Ignite
> Issue Type: Improvement
> Reporter: Kirill Gusakov
> Priority: Major
>
> *Motivation*
> According to
> [comment|https://issues.apache.org/jira/browse/IGNITE-18991?focusedCommentId=17806657&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17806657]
> during the ongoing rebalance we need to use the sum of pending+stable
> assignments as a list of peers for partition raft clients.
> This strategy will protect us in the case, when some tables of zone are
> already rebalanced and should use new stables, but others are still have
> ongoing rebalance.
> *Definition of done*
> - On the rebalance start all RAFT clients for all table partition from this
> zone updates to the clients with pending+stable peers
> - When rebalance is done, RAFT clients switched to the stable assignments only
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
