Joonas Koivunen 138f008bab feat: persistent gc blocking (#8600) ...

Currently, we do not have facilities to persistently block GC on a
tenant for whatever reason. We could do a tenant configuration update,
but that is risky for generation numbers and would also be transient.
Introduce a `gc_block` facility in the tenant, which manages per
timeline blocking reasons.

Additionally, add HTTP endpoints for enabling/disabling manual gc
blocking for a specific timeline. For debugging, individual tenant
status now includes a similar string representation logged when GC is
skipped.

Cc: #6994

2024-08-06 10:09:56 +01:00

..

src

feat: persistent gc blocking (#8600)

2024-08-06 10:09:56 +01:00

Cargo.toml

feat: bare-bones /v1/utilization (#6831)

2024-02-22 13:58:59 +02:00