mirror of
https://github.com/nspcc-dev/neofs-node.git
synced 2026-03-01 04:29:10 +00:00
Meta: handle every notification from block #1392
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#1392
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 @carpawell on GitHub (Mar 28, 2025).
Originally assigned to: @carpawell on GitHub.
Meta relies on order much. Object notifications were synced via raw block handling in #3219. Container creation and deletion are still done via separate subs channels.
Expected Behavior
Container PUT/DELETE can also be a part of the raw block handling and the order of object handling can be straight without any racing.
Current Behavior
Container drop is done via a separate routine as an optimization. (Un)subscription is our usual danger of neo-go's deadlock. Container creation and container removal may have a race.
Possible Solution
Use
nspcc-dev/neofs-node@4f485320f7/pkg/services/meta/notifications.go (L76-L86)for every notification (parsing logic may become a little more complex).Steps to Reproduce (for bugs)
SearchV2 tests with fast container delete/create locked notifications and required kludges.