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

[jira] [Updated] (IGNITE-17935) Finish implementation of streaming RAFT snapshot sender

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

Roman Puchkovskiy updated IGNITE-17935:
---------------------------------------
    Summary: Finish implementation of streaming RAFT snapshot sender  (was: Finish implementation of RAFT streaming snapshot sender)

> Finish implementation of streaming RAFT snapshot sender
> -------------------------------------------------------
>
>                 Key: IGNITE-17935
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17935
>             Project: Ignite
>          Issue Type: Improvement
>          Components: persistence
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> Implementation is started in IGNITE-17083, but the task turned out to be too big for one PR.
> What has to be done:
>  # Serve requests to get snapshot metadata
>  # Switch from sending {{persistedIndex}} as {{lastAppliedIndex}} to sending {{lastAppliedIndex}} itself
>  # When sending {{{}lastAppliedIndex{}}}, take into consideration {{lastAppliedIndex}} of both MV and TX storages
>  # Resolve all TODOs mentioning this issue



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