Meta signature collection in relay scenario #1289

Open
opened 2025-12-28 17:22:28 +00:00 by sami · 1 comment
Owner

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

  • Version used: master
  • Server setup and configuration:
  • Operating System and version (uname -a):
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 * Version used: master * Server setup and configuration: * Operating System and version (`uname -a`):
Author
Owner

@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

@carpawell commented on GitHub (Dec 24, 2024): As we [know](https://github.com/nspcc-dev/neofs-node/pull/3014), "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
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-node#1289
No description provided.