Skip to content

Leaking child objects after parent delete in multishard local storage setup #3551

@cthulhu-rider

Description

@cthulhu-rider

i test how child objects are affected when parent's tombstone is put to the storage engine

i expect that once tombstone is successfully put, all child objects are marked as garbage and after a certain time will be completely removed from storage

Expected Behavior

child objects are handled regardless of number of shards

Current Behavior

works as expected with single shard only. Multiple shards show flaky behavior. I guess outcome depends on sort order

the test may be wrong

Possible Solution

when tombstone arrives, show it to all shards

Steps to Reproduce (for bugs)

see storage engine unit tests in #3549

Context

Regression

not likely

Your Environment

Metadata

Metadata

Assignees

No one assigned

    Labels

    I4No visible changesS3Minimally significantU2Seriously plannedbugSomething isn't workingneofs-storageStorage node application issues

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions