nspcc-dev / nspcc-dev/neofs-node
Sort EC rules by complexity and try simpler ones first
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.
according to EC rules, various number of EC parts (objects) may be produced. Also, ParityPartNum tells max num of parts we can lose. Rules from one policy can differ greatly in the general case
for example, 3/1 and 12/4. For PUT, the first one is simpler in terms of object/RPC num. For GET, 1st one is always simpler/faster
Describe the solution you'd like
when handling EC rules, pre-sort them and handle simpler ones earlier
Additional context
- #526
- #3497
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 with the EC rule definitions in internal/ec/ec.go, then read the context in #526 and #3497. Trace how PUT and GET handling consumes those rules; done means simpler rules are handled earlier for both paths, with behavior verified against the existing project checks.
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
- 38/100