Skip to content
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

delete remote and cleanBackupObjectDisks - slow - need batching and parallelization for delete keys #1066

Open
Slach opened this issue Dec 18, 2024 · 4 comments
Milestone

Comments

@Slach
Copy link
Collaborator

Slach commented Dec 18, 2024

No description provided.

@Slach Slach added this to the 2.7.0 milestone Dec 18, 2024
@Slach Slach changed the title cleanBackupObjectDisks - slow - need batching and parallelization cleanBackupObjectDisks - slow - need batching and parallelization and batching Dec 18, 2024
@Slach Slach changed the title cleanBackupObjectDisks - slow - need batching and parallelization and batching delete remote and cleanBackupObjectDisks - slow - need batching and parallelization for delete keys Jan 15, 2025
@s-b90
Copy link

s-b90 commented Feb 4, 2025

Hi! Thanks for raising this issue. Is there any workaround while waiting new release?
It may take hours in our case to wait for cleanBackupObjectDisks. While backup creates in minutes.
We have tiered storage structure with old parts of tables on s3.

@Slach
Copy link
Collaborator Author

Slach commented Feb 4, 2025

@s-b90 no workaround right now, unfortunatelly
actually root reason is different storage types have different approach for deletion

@s-b90
Copy link

s-b90 commented Feb 4, 2025

Is it possible to set BACKUPS_TO_KEEP_LOCAL=0 and BACKUPS_TO_KEEP_REMOTE=0 and manually delete the extra backups from S3?

I can easily find the remote backup location:
<S3_BUCKET>/<S3_PATH>|<S3_OBJECT_DISK_PATH>//<backup_name>.

However, I’m not sure where the local backups are stored in S3. Could you help me with that?

@Slach
Copy link
Collaborator Author

Slach commented Feb 4, 2025

yes, i forgot, of course this is possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants