nspcc-dev / nspcc-dev/neofs-api
Flexible CBF
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 existing containers can't be stretched to more nodes if needed. Consider a REP 3 CBF 3 container growing from 1TB to 1PB of data, it can easily fit into nine nodes initially, but with 1 PB that's more than 100 TB per node, depending on hardware setup this might be impossible to do.
Describe the solution you'd like
Add some way to have flexible CBF, like magic number in the policy (0?) and an additional attribute that can be changed. Nodes can change for a container and we know the number of them can shrink/extend normally. In that sense changing the CBF seems to be fine if the placement policy is fixed otherwise.
Describe alternatives you've considered
I don't see any.
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
No file, test, or entry point is named. Start by reviewing the API and proto declarations for container placement policies and CBF, then clarify how a mutable CBF and node-count changes should be represented; done requires an agreed design and corresponding API behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100