Neo SPCC has updated the NeoFS node to v0.44.0. The update, now live on the NeoFS TestNet and MainNet, introduces new utility commands, improved FSTree performance, and important bug fixes.
New functionality
The neofs-cli tool now includes two new commands: control object list, which allows users to view objects recognized by a node, and control object revive, which restores objects flagged for deletion.
Additionally, the neofs-lens utility adds the meta last-resync-epoch command to display the last metabase resynchronization time and the fstree cleanup-tmp command to remove temporary files from FSTree.
The team added an improved FSTree writer, which offers an approximate 15% improvement in PUT request performance with minimal overhead on GET requests. In the long-term FSTree will replace peapod substorage; a data migration tool has been provided for existing node runners.
Bug fixes
The v0.44.0 update also addresses key bugs, primarily affecting the storage node. A data corruption problem caused by overly concurrent PUT requests and a panic in the FS chain event listener when unable to switch RPC nodes have been resolved. The update also removes unnecessary network calls related to object expiration decisions.
Neo SPCC also resolved an issue where errors were not being raised for invalid container session token signatures.
Node upgrading
Storage nodes that upgrade to v0.44.0 with the v0.43.0 metabase will experience an automatic, irreversible update.
The new version includes configuration updates such as an option to adjust PUT retry timeouts, a renaming of the “morph” section of the configuration file to “fschain”, and a requirement to replace binary keys with NEP-6 wallets. A guide for migrating keys to wallets can be found here.
Neo SPCC encourages operators to transition to FSTree storage, particularly for smaller storage setups, as the older peapod mechanism is expected to be phased out in the future.
Migration can be completed using the peapod-to-fstree binary included with the release, and users should note that the original peapod database will not be deleted automatically during the process.
The original release notes can be found at the link below:
https://github.com/nspcc-dev/neofs-node/releases/tag/v0.44.0
