nspcc-dev / neofs-node

NeoFS is a decentralized distributed object storage integrated with the Neo blockchain
https://fs.neo.org
GNU General Public License v3.0
32 stars 38 forks source link

Dropping object via control service leaves traces in the metabase #2822

Closed roman-khimov closed 3 months ago

roman-khimov commented 5 months ago

Expected Behavior

neofs-cli control drop-objects removing all data about the object from the node.

Current Behavior

Apparently, some traces are still left in the metabase after it, this:

Apr 20 04:09:14 titan4 neofs-node[420363]: 2024-04-20T04:09:14.760Z warn shard/gc.go:339 iterator over expired locks failed {"shard_id": "2N1drpyfAuTXes7ShXUAF4", "error": "could not parse expiration epoch: strconv.ParseUint: parsing "'or'1'='1": invalid syntax"}

only ends with metabase resync (broken object is deleted via drop-objects).

Possible Solution

Clean up all metabase data on drop-objects.

Steps to Reproduce (for bugs)

Add some broken object (likely not that easy now), delete it, see that GC is still broken.

Context

Testnet.

Your Environment