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

HEAD operation leads to RPC requests #2972

Open
roman-khimov opened this issue Oct 18, 2024 · 2 comments
Open

HEAD operation leads to RPC requests #2972

roman-khimov opened this issue Oct 18, 2024 · 2 comments
Labels
bug Something isn't working I4 No visible changes neofs-storage Storage node application issues S4 Routine U2 Seriously planned
Milestone

Comments

@roman-khimov
Copy link
Member

Expected Behavior

HEAD operation returning result using local data only.

Current Behavior

read object header from NeoFS: status: code = 1024 message = connection to the RPC node has been lost"

Why some RPC request?

Possible Solution

Change something.

Steps to Reproduce (for bugs)

Not known.

Context

Mainnet.

Regression

Doesn't look like.

Your Environment

  • Version used: 0.43.0
  • Operating System and version (uname -a): Debian stable
@roman-khimov roman-khimov added bug Something isn't working neofs-storage Storage node application issues U2 Seriously planned S4 Routine I4 No visible changes labels Oct 18, 2024
@roman-khimov roman-khimov added this to the v0.44.0 milestone Oct 18, 2024
@carpawell
Copy link
Member

Why some RPC request?

But why not? How do you plan to check ACL rules in a general case?

@roman-khimov
Copy link
Member Author

In general yes, it can't be avoided. But in many cases we can avoid additional ones. We know requests from other container nodes immediately, for example and they can't be affected by RPC.

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 S4 Routine U2 Seriously planned
Projects
None yet
Development

No branches or pull requests

2 participants