Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Meta signature collection in relay scenario #3030

Open
roman-khimov opened this issue Nov 26, 2024 · 1 comment
Open

Meta signature collection in relay scenario #3030

roman-khimov opened this issue Nov 26, 2024 · 1 comment
Labels
bug Something isn't working I4 No visible changes neofs-storage Storage node application issues S3 Minimally significant U3 Regular

Comments

@roman-khimov
Copy link
Member

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):
@roman-khimov roman-khimov added bug Something isn't working neofs-storage Storage node application issues U2 Seriously planned S3 Minimally significant I4 No visible changes labels Nov 26, 2024
@roman-khimov roman-khimov added this to the v0.45.0 milestone Nov 26, 2024
@carpawell
Copy link
Member

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

@roman-khimov roman-khimov removed this from the v0.45.0 milestone Dec 24, 2024
@roman-khimov roman-khimov added U3 Regular and removed U2 Seriously planned labels Dec 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working I4 No visible changes neofs-storage Storage node application issues S3 Minimally significant U3 Regular
Projects
None yet
Development

No branches or pull requests

2 participants