nspcc-dev / nspcc-dev/neofs-node
Flexible GC workload
Open
Nobody has claimed this yet.
enhancement
I2
neofs-storage
S2
U4
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
Is your feature request related to a problem? Please describe.
I'm always frustrated when we delete containers with millions objects and it may last for days.
Describe the solution you'd like
Be able to tune the number of objects being deleted based on a current load. If a node does nothing, it may try harder, but if we are being benchmarked, removing objects from disks may be stopped for some time.
Describe alternatives you've considered
-
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating container deletion and garbage-collection code, then determine how current node load should control deletion and how benchmarking can pause it; done means the behavior is specified and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100