You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Bessonov (Jira)" <ji...@apache.org> on 2023/07/10 10:19:00 UTC

[jira] [Resolved] (IGNITE-19852) Deal with RecoveryCompletionFutureFactory

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

Ivan Bessonov resolved IGNITE-19852.
------------------------------------
    Resolution: Duplicate

Duplicates https://issues.apache.org/jira/browse/IGNITE-19778

> Deal with RecoveryCompletionFutureFactory
> -----------------------------------------
>
>                 Key: IGNITE-19852
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19852
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Kirill Tkalenko
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-beta2
>
>
> The main problem is described in IGNITE-19801, but due to the fact that we now have code closely related to updating the configuration revision, it is difficult to do everything at once in IGNITE-19801, so it will be divided into parts.
> As part of ticket IGNITE-19777, we will have a new meta storage recovery mechanism, so we need to do something with *RecoveryCompletionFutureFactory*, I think that in general we can get rid of it, but this needs to be checked more carefully.



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