GC: Implement endpoint to access GC outside of storage engine #121

New issue

Closed

opened 2025-12-28 17:18:29 +00:00 by sami · 0 comments

sami commented

2025-12-28 17:18:29 +00:00

Owner

Originally created by @alexvanin on GitHub (Feb 10, 2021).

Originally assigned to: @cthulhu-rider on GitHub.

Remove data by external invocations via endpoint -- is the simplest case for storage engine garbage collector. Endpoint should provide public method from storage engine to physically remove any existing object. Later this endpoint will be used by Policer component and by external monitors via Control API.

On delete invocation, endpoint should:

find shard that stores the object,
make a GCMARK in graveyard bucket.

To implement this we need:

modify metabase.Ihume() to support GCMARK records

Originally created by @alexvanin on GitHub (Feb 10, 2021). Originally assigned to: @cthulhu-rider on GitHub. Remove data by external invocations via endpoint -- is the simplest case for storage engine garbage collector. Endpoint should provide public method from storage engine to physically remove any existing object. Later this endpoint will be used by `Policer` component and by external monitors via `Control API`. On delete invocation, endpoint should: - find shard that stores the object, - make a GCMARK in graveyard bucket. To implement this we need: - [ ] modify `metabase.Ihume()` to support `GCMARK` records