[
https://issues.apache.org/jira/browse/IGNITE-25602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Korotkov updated IGNITE-25602:
-------------------------------------
Labels: ise (was: )
> ERROR is always logged even if snapshot is created successfully
> ----------------------------------------------------------------
>
> Key: IGNITE-25602
> URL: https://issues.apache.org/jira/browse/IGNITE-25602
> Project: Ignite
> Issue Type: Bug
> Reporter: Sergey Korotkov
> Priority: Minor
> Labels: ise
> Attachments: DucktapeReport-2025-06-05T16_05_59+03_00--122.zip
>
>
> Looks like after the IGNITE-24130 even the successful snapshot creation is
> followed with a ERROR logged like:
> {noformat}
> [2025-06-05T16:15:50,631][ERROR][sys-#47%None%][SnapshotFutureTask] Snapshot
> directory doesn't exist [snpName=test_snapshot,
> dir=/mnt/service/work/db/ducktape_06_sbt_ignite_dev_ru/snp]
> {noformat}
> It may be reproduced say in the
> [./ignitetest/tests/snapshot_test.py|https://github.com/apache/ignite/blob/master/modules/ducktests/tests/ignitetest/tests/snapshot_test.py]
> ducktest.
> Attached are the results running this test against 2.17.0 and current master
> ([https://github.com/apache/ignite/commit/347a4fe63ca579e599fa0c0b1e8b242c18a37c94])
> Server node logs do not contain any errors for 2.17.0.
> On the other hand the current master produces the above ERROR message.
> ***
> Test in general checks the consistency and correctness of the snapshot
> itself. So looks like snapshots as such are not broken.
> It's just false ERROR message.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)