-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[BUG] [OPENSEARCH] [AWS] - Error while deleting snapshot on S3 #14523
Comments
Hello everyone! It can be reproduced with a scenario described by @cuasso (using a snapshot policy) and with the steps described in this case on the OpenSearch forum (delete error if there is more than one snapshot in the repository). I have two clusters (main and sandbox) with the same version 2.17.1 connected to two different MinIO clusters:
To test, I connected my sandbox cluster to the problematic version of Minio and the error was reproduced. I noticed that even if a snapshot is not present in OpenSearch after this delete attempt, its data still exists in the S3 storage. The last snapshot in the repository would be deleted without this error. @andrross, @gbbafna, I would appreciate any help and can provide additional information.
|
Finally solved. "base_path": "my/snapshot/directory"
|
Describe the bug
We are saving a custom snapshot to S3 on AWS. For this purpose, we set up a custom s3 repository and create a policy that takes a daily snapshot and saves it to s3.
We don't have any problem with the save process, but the delete process always throws an error. It's a strange error because we see that the previous snapshot was being deleted, but the process fail.
The error is:
We communicate with our aws support and they said that there isn't a problem with s3 configuration.
Related component
Storage:Snapshots
To Reproduce
Expected behavior
We hope that the snapshots will be deleted and the process will be marked as successful.
Additional Details
S3 repository
Open Search Snapshot policy
Creation/Deletion Status
The text was updated successfully, but these errors were encountered: