[
https://issues.apache.org/jira/browse/IGNITE-17552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17598258#comment-17598258
]
Pavel Pereslegin commented on IGNITE-17552:
-------------------------------------------
[~ivandasch], thanks for the suggestion,
cherry picked into ignite-2.14 branch.
> The snapshot error is not propagated to the initiating node if it is not the
> coordinator.
> -----------------------------------------------------------------------------------------
>
> 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: Major
> Labels: iep-43, ise
> Fix For: 2.15
>
> Attachments: error.log
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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.
> The problem concerns not only metrics, despite the error, the user future
> completes successfully and error does not reach the user.
> Reproducer:
> {code:java}
> startGridsWithCache(2, dfltCacheCfg, CACHE_KEYS_RANGE);
> // Must fail, but on non-coordinator finishes successfully.
>
> grid(1).context().cache().context().snapshotMgr().createSnapshot(SNAPSHOT_NAME,
> "/bad/path").get();
> // Fails (as expected).
>
> grid(0).context().cache().context().snapshotMgr().createSnapshot(SNAPSHOT_NAME,
> "/bad/path").get();
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
