[jira] [Updated] (IGNITE-20640) RAFT client does not change peers after rebalance

["Vladislav Pyatkov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IGNITE-20640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vladislav Pyatkov updated IGNITE-20640:
---------------------------------------
    Summary: RAFT client does not change peers after rebalance  (was: Raft node started in a node where it should not be)

> RAFT client does not change peers after rebalance
> -------------------------------------------------
>
>                 Key: IGNITE-20640
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20640
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Vladislav Pyatkov
>            Priority: Major
>
> Due to nodes starting simultaneously, tests may have several rebalances at the start. After the rebalance is finished, the list of peers for the raft replication group can be different. The changed list of peers should apply to RAFT clients, but it does not happen.
> The method (InternalTableImpl#updateInternalTableRaftGroupService) updates clients only on table start and does not consider a further rebalance. Currently, we try to send a raft command but receive a timeout exception because the leader is absent from the list of peers:



--
This message was sent by Atlassian Jira
(v8.20.10#820010)