Neo SPCC has published NeoFS Node v0.51.1, a follow-up to the v0.51.0 release released earlier this month. The update focuses on new management and diagnostic tools, several storage layer bug fixes, and performance improvements for metabase resynchronization.
NeoFS Node v0.51.1
The v0.51.1 release introduces new CLI commands and a storage node observability metric, in addition to a series of targeted bug fixes and dependency updates.
On the tooling side, a new container policy check command allows operators to verify whether a container’s placement policy can be satisfied by the current network map, providing quick diagnosis for policy misconfiguration. The neofs-adm utility gets two mainchain management commands: mainchain update for upgrading contracts and mainchain version for querying the deployed contract version, streamlining administrative workflows for node operators managing the NeoFS infrastructure on the Neo mainchain.
A new police consistency metric has been added to storage nodes. The metric tracks whether the police have completed a full cycle without performing any object moves, effectively indicating that all objects on the node comply with their placement policy. Once a clean cycle completes, the metric is set to true; on each subsequent move it will be reset to false until a new clean pass is completed. This gives operators an easy way to monitor cluster consistency at the node level.
On the performance side, metabase resynchronization is accelerated through the use of batch operations, which reduces the time required to rebuild the metabase when operators trigger a resynchronization.
Storage nodes now retry notary requests when a insufficient amount of gas An error has occurred, addressing a scenario where container removal could fail due to temporary gas shortages during contract execution. Addresses an issue that occasionally prevented the deletion of containers on the network.
Bug fixes in this release address several storage layer issues. Compressed files in the FSTree are now properly closed after use, preventing resource leakage. A potential payload overflow when retrieving full objects from combined FSTree files has been corrected. The CLI’s default token timestamps have been adjusted to account for network blocking time, fixing frequent token validity errors on TestNet and MainNet where the previous defaults were too tight. Repeated garbage collection attempts to remove objects that no longer exist are now suppressed, and address changes in the node configuration now correctly trigger a netmap update instead of being silently ignored. Finally, a billing fix was applied to networks migrating contracts from version 0.25.0 to 0.26.0, with the neofs contract dependency updated to v0.26.1 to include the fix.
The NeoGo dependency has been updated to v0.117.0.
Guidance on upgrades
NeoFS Node v0.51.1 is a simple update to v0.51.0 without major configuration changes. Operators with v0.51.0 can upgrade on the spot. Those still on v0.50.x should follow the migration guidelines published with the v0.51.0 release, including removing outdated Inner Ring configuration options and completing any outstanding metabase migrations before upgrading.
The full changelog and release notes can be found via the link below:
https://github.com/nspcc-dev/neofs-node/releases/tag/v0.51.1