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

Enhancement: Configure reapers to distribute deletions evenly instead of in periodic bursts #829

Open
dynamic-entropy opened this issue Jul 23, 2024 · 1 comment
Assignees

Comments

@dynamic-entropy
Copy link
Contributor

Enhancement Description

Sites with slow deletions struggle during high loads, often exceeding storage capacity and failing to catch up. We need to optimize reaper configuration and scheduling to address this issue. This enhancement should consider factors such as site-specific deletion latency and deletion backlog.

  • In addition, auto-scaling and deploying reapers for specific sites during emergency high loads would be highly beneficial.

Use Case

During peak usage times, a site with slow deletions risks exceeding its storage capacity. Optimized reaper configurations and work scheduling will help manage deletions more efficiently.

  • Automatic scaling and deployment of reapers will ensure that deletion processes keep pace with increased writes. This will also eliminate the manual workload for operators.

Possible Solution

No response

Related Issues

No response

@labkode
Copy link

labkode commented Aug 15, 2024

Related to rucio/rucio#6512

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

No branches or pull requests

2 participants