Provide subscriptions to network config changes #182

New issue

Open

opened 2025-12-28 18:08:47 +00:00 by sami · 4 comments

sami commented

2025-12-28 18:08:47 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Aug 8, 2024).

there is no current way to subscribe to changes of the NeoFS network settings. This would improve the system's reaction to reconfigs

Describe the solution you'd like

throw per-config notificaitons by the Netmap contract and subscribe to them from the app side

Describe alternatives you've considered

polling, i.e. long delays and often idle requests

Additional context

Originally created by @cthulhu-rider on GitHub (Aug 8, 2024). ## Is your feature request related to a problem? Please describe. there is no current way to subscribe to changes of the NeoFS network settings. This would improve the system's reaction to reconfigs ## Describe the solution you'd like throw per-config notificaitons by the Netmap contract and subscribe to them from the app side ## Describe alternatives you've considered polling, i.e. long delays and often idle requests ## Additional context * https://github.com/nspcc-dev/neofs-node/issues/2910 * #372

sami added the

netmap

feature

labels

2025-12-28 18:08:47 +00:00

sami commented

2025-12-28 18:08:48 +00:00

Author

Owner

@carpawell commented on GitHub (Aug 9, 2024):

What it such a notification is missed?

@carpawell commented on GitHub (Aug 9, 2024): What it such a notification is missed?

sami commented

2025-12-28 18:08:48 +00:00

Author

Owner

@cthulhu-rider commented on GitHub (Aug 9, 2024):

wont get any worse than when there are no notifications at all

@cthulhu-rider commented on GitHub (Aug 9, 2024): wont get any worse than when there are no notifications at all

sami commented

2025-12-28 18:08:48 +00:00

Author

Owner

@carpawell commented on GitHub (Aug 9, 2024):

I meant it may get better but the current node code expects to miss any number of notifications at any time, so we cannot rely on it until some changes are done on the nodes side.

@carpawell commented on GitHub (Aug 9, 2024): I meant it may get better but the current node code expects to miss any number of notifications at any time, so we cannot rely on it until some changes are done on the nodes side.

sami commented

2025-12-28 18:08:48 +00:00

Author

Owner

@cthulhu-rider commented on GitHub (Aug 9, 2024):

practice shows network config changes extremely rarely. With notifications, nodes could use bigger cache time and catch changes by notifications mostly. Yeah, running node can miss a notification, and it will know about the change later. But normally notifications should not be missed. And this seems a better option than more frequent requests when config stays the same for months

so, worst scenario is not worse while the best one is better. And ur right, this will definitely require catch implementation. The costs seem negligible

@cthulhu-rider commented on GitHub (Aug 9, 2024): practice shows network config changes extremely rarely. With notifications, nodes could use bigger cache time and catch changes by notifications mostly. Yeah, running node can miss a notification, and it will know about the change later. But normally notifications should not be missed. And this seems a better option than more frequent requests when config stays the same for months so, worst scenario is not worse while the best one is better. And ur right, this will definitely require catch implementation. The costs seem negligible