You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2022/08/29 09:50:00 UTC
[jira] [Assigned] (IGNITE-17552) Empty SnapshotErrorMessage on non-coordinator node
[ https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Pereslegin reassigned IGNITE-17552:
-----------------------------------------
Assignee: Pavel Pereslegin
> Empty SnapshotErrorMessage on non-coordinator node
> --------------------------------------------------
>
> Key: IGNITE-17552
> URL: https://issues.apache.org/jira/browse/IGNITE-17552
> Project: Ignite
> Issue Type: Bug
> Affects Versions: 2.13
> Reporter: Stepanov Ilya
> Assignee: Pavel Pereslegin
> Priority: Minor
> Labels: ise
> Attachments: error.log
>
>
> In some cases, when we execute "createSnapshot" on non-coordinator node, the snapshot error is not reported in the "LastSnapshotErrorMessage" metric, but the "LastSnapshotStartTime" and "LastSnapshotErrorMessage" metrics are updated.
> This is misleading that the snapshot was taken successfully.
> Steps to reproduce:
> 1) Create cluster with 2+ nodes
> 2) execute "createSnapshot" with non-existent path(example: /bad/path) on non-coordinator node
> 3) check "LastSnapshotErrorMessage" on non-coordinator node
> 4) execute "createSnapshot" with non-existent path on coordinator node
> 5) check "LastSnapshotErrorMessage" coordinator node
--
This message was sent by Atlassian Jira
(v8.20.10#820010)