Meta: handle every notification from block #1392

Closed
opened 2025-12-28 17:22:50 +00:00 by sami · 0 comments
Owner

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.

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 https://github.com/nspcc-dev/neofs-node/blob/4f485320f7ec8122177c0da554667d909f4432de/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](https://github.com/nspcc-dev/neofs-testcases/pull/997) with fast container delete/create locked notifications and required kludges.
sami 2025-12-28 17:22:50 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
nspcc-dev/neofs-node#1392
No description provided.