nspcc-dev / nspcc-dev/neofs-api
Policy for reduced redundancy EC split
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 11
- Forks
- 15
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 9
Description
Is your feature request related to a problem? Please describe.
I'm always frustrated when we can't specify the minimum number of parts to be laid to disks for a successful PUT. Right now there is no notion of it, for 12+4 policy 16 objects have to be added while in some cases users are OK with 14 (cluster has 16 nodes and one or two are unavailable).
Describe the solution you'd like
Have some EC-specific "MINPARTS" number in policy rule.
Describe alternatives you've considered
Can be a part of initial placement policy, although initial placement is designed more as optimization and currently it just enables/disables a certain EC rule. However it's pretty close in mechanics.
REP rules can also be thought of wrt this.
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 policy rule definitions and reviewing how initial placement and REP rules are represented. Clarify whether MINPARTS belongs in the EC-specific rule or initial placement policy, then define the expected behavior for a 12+4 policy when fewer than 16 parts are available.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100