Skip to content

Limit TOMBSTONE members number to one #311

@carpawell

Description

@carpawell

Is your feature request related to a problem? Please describe.

I'm always frustrated when there is only a single object in the DELETE RPC but a lot of objects are in the tombstone's body. It is even more unexpected after #297 (however, it is not that clear when we are cleaning unfinished big objects).

Describe the solution you'd like

Disallow "big" tombstones. One TS -- one object. Tombstones expire sooner or later and tombstones with many objects are not expected, it is even not possible currently due to DELETE RPC, only if someone creates it manually.

Describe alternatives you've considered

Keep it as is.

Additional context

Uncontrollable number of deleted objects by a single object makes it harder to maintain object meta information: nspcc-dev/neofs-contract#448 (comment).

Metadata

Metadata

Assignees

No one assigned

    Labels

    I2Regular impactS2Regular significanceU3RegularenhancementImproving existing functionality

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions