Node stops seeing previously stored objects if dir naming pattern changes in blobstor #101

New issue

Open

opened 2023-03-08 23:34:09 +00:00 by snegurochka · 0 comments

snegurochka commented

2023-03-08 23:34:09 +00:00

Member

Original issue: https://github.com/nspcc-dev/neofs-node/issues/2174

In current implementation Blobstor reads objects from the underlying FSTree according to DirNameLen application config value.

If application changes this value, previously stored objects can not be read from the node anymore.

Expected Behavior

Data are still available.

Current Behavior

Node starts as empty.

Possible Solution

Node should either:

restruct already stored data in FSTree on startup
allow mixing and have ability to read objects from both dir naming formats

Steps to Reproduce (for bugs)

Run NeoFS with storage nodes v0.28.1
Restart NeoFS with storage nodes v0.34.0

Context

NeoFS Testnet/Mainnet investigations.

Your Environment

Version used: v0.28.1 -> v0.34.0

Original issue: https://github.com/nspcc-dev/neofs-node/issues/2174 In current implementation `Blobstor` reads objects from the underlying `FSTree` according to [DirNameLen](https://github.com/nspcc-dev/neofs-node/blob/694d8882193fe259858f2bb2c8be91ae58d8cab4/pkg/local_object_storage/blobstor/fstree/fstree.go#L29) application config value. If application changes this value, previously stored objects can not be read from the node anymore. ## Expected Behavior Data are still available. ## Current Behavior Node starts as empty. ## Possible Solution Node should either: * restruct already stored data in FSTree on startup * allow mixing and have ability to read objects from both dir naming formats ## Steps to Reproduce (for bugs) 1. Run NeoFS with storage nodes `v0.28.1` 2. Restart NeoFS with storage nodes `v0.34.0` ## Context NeoFS Testnet/Mainnet investigations. ## Your Environment * Version used: **v0.28.1** -> **v0.34.0**