Skip to content

v0.57.0 - Bido

Latest

Choose a tag to compare

@roman-khimov roman-khimov released this 30 Sep 10:58
4c813ae

Added

  • Online FSTree layout reshaping via the blobstor.allow_depth_change configuration option (#4149, #4179)
  • SN now serves ReplicateV2 API (#4168, #4164, #4201, #4164)
  • Container SN now uses ReplicateV2 API for objects >256K in PUT handler when available (#4168, #4196, #4203)
  • neofs-adm fschain netmap command to fetch current and historical network maps (#4181)
  • Container revisions support (#4183, #4195, #4197)

Fixed

  • Broken EC object GET with all data parts missing (#4173)
  • Buffer race of EC part range request buffers in GET server (#4176)

Changed

  • SN requests network map only when it has been changed (#4121)
  • SN pushes URI-style endpoints to netmap instead of multiaddr (#3982)
  • Write-cache FSTree depth increased from 1 to 2 with online migration (#4175)
  • Policer balances data across local shards (#4170)
  • neofs-adm fschain set-config now suggests well-known keys in shell completion (#1901)
  • Write cache now flushes object dynamically based on taken space (#3415)

Removed

  • GetRange object service method (#4167)
  • Metabase migration code for DB version 10 (from 9) (#4184)
  • __NEOFS__NONCE attribute from metabase (#4187)

Updated

  • github.com/nspcc-dev/neofs-contracts module to v0.27.0 (#4121, #4195)
  • google.golang.org/grpc dependency from 1.83.1 to 1.83.2 (#4169)
  • github.com/nspcc-dev/neofs-sdk-go module to v1.0.0-rc.23 (#4168, #4187, #4193, #4197, #4202)

Updating from v0.56.0

To change an FSTree layout depth, configure the new blobstor.depth and set blobstor.allow_depth_change to true, then restart the storage node. After the node logs that reshaping has completed, the flag can be removed.

Network maps with 0.56.0 nodes can differ from previous ones because of address conversion from multiaddr. Multiaddr is still accepted by IR and SN, but this support will be removed in the next release.

All applications should be updated to use parameterized Get instead of GetRange method since this version doesn't support GetRange.

Metabase migration for version 10 introduced in NeoFS node 0.52.0 was removed from this release, upgrade to 0.56.0 first if using earlier versions or resynchronize metabases.

This release introduces metabase version 12 with minor changes to the old version. Metabases will be migrated automatically on node startup, but this can take some time for large shards with many objects.