Neo SPCC has revealed NeoFS Node v0.51.1, a follow-up to the v0.51.0 launch shipped earlier this month. This replace focuses on new administration and diagnostic instruments, a number of storage layer bug fixes, and efficiency enhancements for metabase resync.
NeoFS Node v0.51.1
The v0.51.1 launch introduces new CLI instructions and storage node observability metrics, along with a set of focused bug fixes and dependency updates.
On the device aspect, new container coverage verify instructions permit operators to confirm whether or not container placement insurance policies will be met with the present community map, permitting them to shortly diagnose coverage misconfigurations. of neofs-adm This utility provides two mainchain administration instructions: replace mainchain to improve contracts and mainchain model to question the deployed contract model, streamlining the executive workflow for node operators who handle NeoFS infrastructure on the Neo mainchain.
A brand new policer consistency state metric has been added to storage nodes. This metric tracks whether or not the policer completes a whole cycle with out performing any object relocation, successfully signaling that every one objects on the node are compliant with the position coverage. As soon as the clear cycle is full, the metric is ready to true. Subsequent relocations will reset it to false till one other clear move is accomplished. This provides operators a simple solution to monitor cluster consistency on the node degree.
By way of efficiency, using batch operations quickens metabase resynchronization and reduces the time required to rebuild the metabase when an operator triggers a resynchronization.
Storage nodes now retry Notary requests within the following instances: inadequate quantity of fuel Addressed a state of affairs the place container deletion might fail on account of an error and momentary fuel scarcity throughout contract execution. This resolves a difficulty that intermittently prevented containers from being deleted on the community.
Bug fixes on this launch resolve a number of points with the storage layer. Compressed recordsdata in FSTree at the moment are correctly closed after use, stopping useful resource leaks. Fastened a attainable payload overflow when retrieving a whole object from a mixed FSTree file. The CLI’s default token timestamps have been adjusted to account for community blocking instances, resolving frequent token validity errors on TestNet and MainNet the place the earlier defaults had been too strict. Rubbish assortment’s repeated makes an attempt to take away non-existent objects at the moment are suppressed, and node configuration handle adjustments now appropriately set off netmap updates as an alternative of being silently ignored. Lastly, a billing repair was utilized to networks that migrated contracts from model 0.25.0 to 0.26.0, and the neofs-contracts dependency was up to date to v0.26.1 to include the repair.
NeoGo dependencies up to date to v0.117.0.
Improve steering
NeoFS Node v0.51.1 is a direct replace from v0.51.0 with no breaking configuration adjustments. Operators working v0.51.0 can improve as is. If you’re nonetheless utilizing v0.50.x, you need to observe the migration steering revealed within the v0.51.0 launch, together with eradicating deprecated internal ring configuration choices and finishing any excellent metabase migrations earlier than upgrading.
The entire changelog and launch property can be found on the hyperlink under.
https://github.com/nspcc-dev/neofs-node/releases/tag/v0.51.1
