You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Maksim Timonin (Jira)" <ji...@apache.org> on 2023/05/25 15:01:00 UTC

[jira] [Updated] (IGNITE-19567) Wrong consistentId is used for verifying incremental snapshot

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

Maksim Timonin updated IGNITE-19567:
------------------------------------
    Labels: IEP-89  (was: )

> Wrong consistentId is used for verifying incremental snapshot
> -------------------------------------------------------------
>
>                 Key: IGNITE-19567
>                 URL: https://issues.apache.org/jira/browse/IGNITE-19567
>             Project: Ignite
>          Issue Type: Bug
>    Affects Versions: 2.15
>            Reporter: Maksim Timonin
>            Priority: Major
>              Labels: IEP-89
>
> 1.start a node with consistentId A;
> 2.insert some data;
> 3../control.sh --snapshot create full
> 4.kill A;
> 5.start a node with consistentId B;
> 6../control.sh --snapshot restore full.
> this is OK.
> But, if an incremental snapshot is created, an error will be reported during recovery:
> 1.start a node with consistentId A;
> 2.insert some data;
> 3../control.sh --snapshot create full --incremental
> 4.kill A;
> 5.start a node with consistentId B;
> 6../control.sh --snapshot restore full --increment 1.
> There is a wrong check. It verifies that increments match the full snapshot. But instead of getting consistentId from the full snapshot metafile, it gets it from the local node.
>  



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