Object header is not accounted for when evaluating container size #1511

New issue

Open

opened 2025-12-28 17:35:41 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:35:41 +00:00

Owner

Originally created by @roman-khimov on GitHub (Oct 1, 2025).

Expected Behavior

Object has full size, header+payload, that's what we store and that's the disk space used by this object.

Current Behavior

Only payload size is counted for container size metrics and submissions.
nspcc-dev/neofs-node@582380b995/pkg/local_object_storage/metabase/put.go (L94)

Possible Solution

Count headers as well.

Think of counting temporary objects like locks and tombstones, they do require space and it's a vector for DoS.

Context

#3519, basic income.

Regression

No. It was always like that since 41578001e4.

Originally created by @roman-khimov on GitHub (Oct 1, 2025). ## Expected Behavior Object has full size, header+payload, that's what we store and that's the disk space used by this object. ## Current Behavior Only payload size is counted for container size metrics and submissions. https://github.com/nspcc-dev/neofs-node/blob/582380b995ff920c1cd4fe1384abb84e538dd4e8/pkg/local_object_storage/metabase/put.go#L94 ## Possible Solution Count headers as well. Think of counting temporary objects like locks and tombstones, they do require space and it's a vector for DoS. ## Context #3519, basic income. ## Regression No. It was always like that since 41578001e420492f70137e2ed07222c11ef5bdb3.