mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
How to deal with REP 0 policy? #874
Labels
No labels
I1
I2
I3
I4
S0
S1
S2
S3
S4
U0
U1
U2
U3
U4
blocked
bug
config
dependencies
discussion
documentation
enhancement
enhancement
epic
feature
go
good first issue
help wanted
neofs-adm
neofs-cli
neofs-cli
neofs-cli
neofs-ir
neofs-lens
neofs-storage
neofs-storage
performance
question
security
task
test
windows
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
nspcc-dev/neofs-node#874
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cthulhu-rider on GitHub (Nov 11, 2022).
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 replicasTechnically the behavior is expected, but from the user perspective I'd consider this policy as invalid.
@carpawell commented on GitHub (Nov 11, 2022):
If a solution to that issue is somewhere near the policy validation in any of our components, #2038 is related to that too, and could be solved together.
@fyrchik commented on GitHub (Nov 11, 2022):
To me it looks like a nice case to test our system (nobody panics, no space is used).
But we could also validate such things in neofs-cli.
@roman-khimov commented on GitHub (Dec 21, 2023):
A check in CLI can be nice to have (with ability to
--force).