nspcc-dev / nspcc-dev/neofs-node
Allow forcing GC work via SN's control API
Open
Nobody has claimed this yet.
discussion
I3
neofs-cli
neofs-storage
S3
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 have sleeps in our test just to be sure GC has iterated for sure. This may also help in some debug cases on public nodes if some huge garbage cleanup is needed. It also may override GC batch size for one iteration.
Describe the solution you'd like
Add control call that forces SN to GC right now.
Describe alternatives you've considered
Keep sleeps in tests.
Additional context
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
Start by locating the SN control API entry points and the garbage-collection implementation in the repository. Review neofs-testcases/pull/1163 for the testing context, then define completion as a control call that triggers GC immediately and supports the requested one-iteration behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100