You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mirza Aliev (Jira)" <ji...@apache.org> on 2025/10/03 13:23:00 UTC

[jira] [Updated] (IGNITE-25543) Implement retry mechanism for resetPeers

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

Mirza Aliev updated IGNITE-25543:
---------------------------------
    Labels: MakeTeamcityGreenAgain ha-instability ignite-3  (was: MakeTeamcityGreenAgain ignite-3)

> Implement retry mechanism for resetPeers
> ----------------------------------------
>
>                 Key: IGNITE-25543
>                 URL: https://issues.apache.org/jira/browse/IGNITE-25543
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Mirza Aliev
>            Assignee:  Kirill Sizov
>            Priority: Major
>              Labels: MakeTeamcityGreenAgain, ha-instability, ignite-3
>          Time Spent: 2.5h
>  Remaining Estimate: 0h
>
> h3. Motivation
> Currently, {{resetPeers}} intent from {{resetPartitions}} tries to reset peers only once, meaning that if raft is busy for some configuration change, the reset peers intent will be skipped and won't be retried. That leads to loosing {{resetPartitions}} intent, and for HA case that leads to loosing availability. 
> We need to retry reset peers intents in order to achieve resetting raft configuration. 
> h3. Definition of Done
> * Mechanism for retrying {{resetPeers}} intents is implemented.



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