-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SnapshotServiceImpl: no error/warning on failed snapshot deletion #10676
Comments
anatol-sialitski
added a commit
that referenced
this issue
Dec 10, 2024
anatol-sialitski
added a commit
that referenced
this issue
Dec 10, 2024
anatol-sialitski
added a commit
that referenced
this issue
Dec 10, 2024
anatol-sialitski
added a commit
that referenced
this issue
Dec 10, 2024
anatol-sialitski
added a commit
that referenced
this issue
Dec 10, 2024
anatol-sialitski
added a commit
that referenced
this issue
Dec 11, 2024
anatol-sialitski
added a commit
that referenced
this issue
Dec 11, 2024
anatol-sialitski
added a commit
that referenced
this issue
Dec 11, 2024
anatol-sialitski
added a commit
that referenced
this issue
Dec 11, 2024
anatol-sialitski
added a commit
that referenced
this issue
Dec 11, 2024
anatol-sialitski
added a commit
that referenced
this issue
Dec 11, 2024
anatol-sialitski
added a commit
that referenced
this issue
Dec 11, 2024
ashklianko
pushed a commit
that referenced
this issue
Dec 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
App-snapshotter runs scheduled cleanup once an hour by default, and that cleanup may fail silently in elastic with no trace in our logs if other snapshot is being created in the moment. I managed to manually reproduce the issue and catch the exception:
ConcurrentSnapshotExecutionException[[enonic-xp-snapshot-repo:com.enonic.app.snapshotter--hourly2_2024-09-06t07_34_00.244781700z] another snapshot is currently running cannot delete]
Can wrap invocation of
doDeleteSnapshot
with try-catch block and logging within, or maybe the team can propose other solutions to this.The text was updated successfully, but these errors were encountered: