Neo SPCC has published NeoFS Node v0.51.1, a follow-up to the v0.51.0 release shipped earlier this month. This update focuses on new management and diagnostic tools, several storage layer bug fixes, and performance improvements for metabase resync.
NeoFS Node v0.51.1
The v0.51.1 release introduces new CLI commands and storage node observability metrics, in addition to a set of targeted bug fixes and dependency updates.
On the tool side, new container policy check commands allow operators to verify whether container placement policies can be met with the current network map, allowing them to quickly diagnose policy misconfigurations. of neofs-adm This utility adds two mainchain management commands: update mainchain to upgrade contracts and mainchain version to query the deployed contract version, streamlining the administrative workflow for node operators who manage NeoFS infrastructure on the Neo mainchain.
A new policer consistency state metric has been added to storage nodes. This metric tracks whether the policer completes a complete cycle without performing any object relocation, effectively signaling that all objects on the node are compliant with the placement policy. Once the clean cycle is complete, the metric is set to true. Subsequent relocations will reset it to false until another clean pass is completed. This gives operators an easy way to monitor cluster consistency at the node level.
In terms of performance, the use of batch operations speeds up metabase resynchronization and reduces the time required to rebuild the metabase when an operator triggers a resynchronization.
Storage nodes now retry Notary requests in the following cases: insufficient amount of gas Addressed a scenario where container deletion could fail due to an error and temporary gas shortage during contract execution. This resolves an issue that intermittently prevented containers from being deleted on the network.
Bug fixes in this release resolve several issues with the storage layer. Compressed files in FSTree are now properly closed after use, preventing resource leaks. Fixed a possible payload overflow when retrieving a complete object from a combined FSTree file. The CLI’s default token timestamps have been adjusted to account for network blocking times, resolving frequent token validity errors on TestNet and MainNet where the previous defaults were too strict. Garbage collection’s repeated attempts to remove non-existent objects are now suppressed, and node configuration address changes now correctly trigger netmap updates instead of being silently ignored. Finally, a billing fix was applied to networks that migrated contracts from version 0.25.0 to 0.26.0, and the neofs-contracts dependency was updated to v0.26.1 to incorporate the fix.
NeoGo dependencies updated to v0.117.0.
Upgrade guidance
NeoFS Node v0.51.1 is a direct update from v0.51.0 with no breaking configuration changes. Operators running v0.51.0 can upgrade as is. If you are still using v0.50.x, you should follow the migration guidance published in the v0.51.0 release, including removing deprecated inner ring configuration options and completing any outstanding metabase migrations before upgrading.
The complete changelog and release assets are available at the link below.
https://github.com/nspcc-dev/neofs-node/releases/tag/v0.51.1
