[
https://issues.apache.org/jira/browse/IGNITE-17013?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551474#comment-17551474
]
Alexander Lapin commented on IGNITE-17013:
------------------------------------------
[~maliev] LGTM
> Implement failure handling for changePeerAsync invocation regarding rebalance
> algorithm
> -----------------------------------------------------------------------------------------
>
> Key: IGNITE-17013
> URL: https://issues.apache.org/jira/browse/IGNITE-17013
> Project: Ignite
> Issue Type: Task
> Reporter: Mirza Aliev
> Assignee: Mirza Aliev
> Priority: Major
> Labels: ignite-3
>
> According to the relalance algorithm
> https://github.com/apache/ignite-3/blob/main/modules/table/tech-notes/rebalance.md
> after leader node receives an updating of a pending key, it starts a raft
> group reconfiguration by calling {{RaftGroupService#changePeersAsync}} which
> returns future, that can be completed exceptionally. We should provide the
> way to retry {{RaftGroupService#changePeersAsync}} invocation, with some
> throttling, and in case of failure cancel the current rebalance.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
