mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
Meta signature collection in relay scenario #1289
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#1289
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 @roman-khimov on GitHub (Nov 26, 2024).
Expected Behavior
When a node is just a relayer (it doesn't store an object) it should still collect/push meta signatures since it's the one responsible for replication.
Current Behavior
Only "local node" handles signatures.
Possible Solution
Fix it.
Context
#2878, #3029.
Your Environment
uname -a):@carpawell commented on GitHub (Dec 24, 2024):
As we know, "relay" works only in external slicing/full object complete cases and we have not experienced such problems for years and only after we saw our own objects from neo-go team we failed for the first time. It is currently impossible to collect any signatures due to the API that is used in relay (PUT, not REPLICATE), also relay uses all the nodes and takes part in placement logic. I suggest paraphrasing the issue to "fix the relay process" to make it more natural and changing its priority. Not expect problems from our clients for now. @roman-khimov