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/01/09 12:15:00 UTC

[jira] [Updated] (IGNITE-24106) Propagate raft index to onNewPeersConfigurationApplied

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

Mirza Aliev updated IGNITE-24106:
---------------------------------
    Summary: Propagate raft index to onNewPeersConfigurationApplied  (was: Propagate raft index to doStableKeySwitch)

> Propagate raft index to onNewPeersConfigurationApplied
> ------------------------------------------------------
>
>                 Key: IGNITE-24106
>                 URL: https://issues.apache.org/jira/browse/IGNITE-24106
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Mirza Aliev
>            Assignee: Mirza Aliev
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> h3. Motivation
> For the purposes of https://issues.apache.org/jira/browse/IGNITE-23869 we need to know index on which raft changed configuration. This information must be propagated {{onNewPeersConfigurationApplied}} callback from raft, so we could persist it in {{doStableKeySwitch}}
> h3. Implementation details 
> Form the raft side, we could use {{node.conf.getId()}} when we call listener {{onNewPeersConfigurationApplied}} 
> h3. Definition of done
> * Any time raft is reconfigured index of this entry from raft must be returned in {{onNewPeersConfigurationApplied}}
>  



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