nspcc-dev / nspcc-dev/neofs-node
How to deal with `REP 0` policy?
Open
Nobody has claimed this yet.
enhancement
good first issue
I3
neofs-cli
S4
U4
- Dominant language
- Go
- Stars
- 38
- Forks
- 51
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 38
Description
In current implementation zero replication policy is not prohibited by the system:
PUTsucceeds since it has nothing to doGETfails withOBJECT_NOT_FOUNDsince there are no replicas
Technically the behavior is expected, but from the user perspective I'd consider this policy as invalid.
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 how replication policies are validated and how PUT and GET handle a replication factor of zero. Clarify whether zero should be rejected as invalid, then define completion around consistent behavior and tests for policy creation, PUT, and GET.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100