Neo SPCC has released NeoFS node v0.45.0, removing limits on storage node quantities and improving search capabilities.
New improvements
In v0.44.2, NeoFS networks have a limit of approximately 320 storage nodes. An updated network map structure has been introduced in the new version to remove this limit. Additionally, the ObjectService.SearchV2 API has been added, improving search functionality for storage nodes.
Other improvements include new commands for distributed setting management, increased write-cache efficiency, and various bug fixes.
The upgrade has been deployed on the NeoFS TestNet, with a MainNet upgrade scheduled in two weeks.
Upgrading from v0.44.2
Node operators upgrading from v0.44.2 must consider several changes. The use of public keys as rule targets in eACL tables is deprecated; this version will now enforce the use of addresses for rules instead.
BoltDB has also been removed, leading to the elimination of related parameters from the writecacheconfig. Database migration will occur automatically upon upgrade.
In existing nodes, the original network map is still maintained and used by default until the network-wide UseNodeV2 setting is adjusted. As storage nodes add records to both lists by default, IR nodes must be updated first or storage nodes will fail to bootstrap. This can be monitored using the neofs-adm tool to ensure all nodes have been migrated to the new list prior to storage node upgrade.
The full changelog can be read at the following link:
https://github.com/nspcc-dev/neofs-node/releases/tag/v0.45.0
About The Author: Brett Rhodes
Brett is a blockchain enthusiast and freelance writer who originally began producing content for the gaming & eSports industries. Now he spends most of his time contributing in the Neo ecosystem.
More posts by Brett Rhodes