mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
SN starts refusing to save some objects after MaxObjectSize increase #1247
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#1247
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 (Aug 8, 2024).
MaxObjectSizenetwork setting limits payload size of physically stored NeoFS objects. Storage nodes deny bigger objects. By default, value is64M. It may be increased by the IRExpected Behavior
objects not bigger than the current setting are always accepted
Current Behavior
objects with payload bigger than the starttime limit are denied after config increase in runtime
Possible Solution
listen to net config changes and tune server according to it
Steps to Reproduce (for bugs)
see test. Briefly:
L1 = 64Mobject payload limitL2 > L1> L1Context
nspcc-dev/neofs-node@450c4e5ed8/cmd/neofs-node/grpc.go (L60-L61)Regression
no
Your Environment
neofs-node@v0.42.1@roman-khimov commented on GitHub (Aug 26, 2024):
Please upstream your grpc changes and let's see how it goes there.