nspcc-dev/neofs-node

How to deal with `REP 0` policy?

Open

#2,042 opened on Nov 11, 2022

View on GitHubContributor guide
 (3 comments) (0 reactions) (0 assignees)Go (49 forks)auto 404
I3S4U4enhancementgood first issueneofs-cli

Repository metrics

Stars
 (36 stars)
PR merge metrics
 (PR metrics pending)

Description

In current implementation zero replication policy is not prohibited by the system:

  • PUT succeeds since it has nothing to do
  • GET fails with OBJECT_NOT_FOUND since there are no replicas

Technically the behavior is expected, but from the user perspective I'd consider this policy as invalid.

Contributor guide

Research direction
Investigate where the REP policy is validated during PUT and GET operations, and add a check to reject REP 0 as invalid.
Tech stack
go
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50