mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
Policer drops tombstones from backup container SN #1507
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#1507
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 (Sep 19, 2025).
both TOMBSTONE (T) and LOCK (L) are broadcast on PUT
nspcc-dev/neofs-node@eb3ee42f1b/pkg/services/object/put/distributed.go (L177)then, if there are more container SN than REP rule, Policer on each backup SN detects the redundancy and removes T
unlike T, L is kept (
634792077e)Expected Behavior
L and T behave the same way, i.e. T are kept on all container SN
Current Behavior
T behaves like REGULAR object, i.e. dropped on REP rule excess
Possible Solution
make Policer to handle T like L
Steps to Reproduce (for bugs)
REP 2Context
#526
Regression
no
Your Environment