morph: increase buffer for notification handling routines

10 is too low value for practice. It is not mind-blowing to receive tens of notifications per block and, moreover, it was already seen in real networks. Refs #3007. Signed-off-by: Pavel Karpy <[email protected]>
nspcc-dev · Dec 6, 2024 · 6b648df · 6b648df
1 parent 9144021
commit 6b648df
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 2 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -9,6 +9,7 @@ Changelog for NeoFS Node
 - Fail gracefully on error from config validation (#3037)
 
 ### Changed
+- Number of cuncurrenly handled notifications from the chain was increased from 10 to 100 (#3043)
 
 ### Removed
 

diff --git a/cmd/neofs-node/morph.go b/cmd/neofs-node/morph.go
@@ -66,7 +66,7 @@ func listenMorphNotifications(c *cfg) {
 	// the client cannot make RPC requests if
 	// the notification channel is not being
 	// read by another goroutine.
-	const listenerPoolCap = 10
+	const listenerPoolCap = 100
 
 	lis, err := event.NewListener(event.ListenerParams{
 		Logger:             c.log,

diff --git a/pkg/morph/event/listener.go b/pkg/morph/event/listener.go
@@ -575,7 +575,7 @@ func NewListener(p ListenerParams) (Listener, error) {
 	// defaultPoolCap is a default worker
 	// pool capacity if it was not specified
 	// via params
-	const defaultPoolCap = 10
+	const defaultPoolCap = 100
 
 	switch {
 	case p.Logger == nil: