nspcc-dev / nspcc-dev/neofs-node
Parallel processing of policy rules in object PUT
Nobody has claimed this yet.
- 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.
container policy may include several placement policies. Currently, these are multiple REP rules. With #3420, there may also be several EC rules
currently, rules are handled sequentially. Although they are completely independent
Describe the solution you'd like
process rules concurrently. If any routine fails, whole process should be stopped and operation fail. Unleash power of https://pkg.go.dev/golang.org/x/sync/errgroup#Group for this
Describe alternatives you've considered
keep single threading
Additional context
#526
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 tracing object PUT handling to find where placement policy rules are processed, then review the context from #3420 and #526. Check how golang.org/x/sync/errgroup can coordinate the independent rules. Done means rules run concurrently and any failed routine stops the operation and causes the PUT to fail.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100