Allow doctor to restore/drop objects on a per-container basis #573

New issue

Open

opened 2023-08-07 12:25:25 +00:00 by fyrchik · 0 comments

fyrchik commented

2023-08-07 12:25:25 +00:00

Owner

The rationale is to postpone object deletion is some cases an do it manually.
We also need some listing capabilities: if blockchain is unavailable, we still want to diagnose what is happening. Metrics are OK, but not verbose. frostfs-lens doesn't work unless the service is stopped (it needs exclusive access to the database).

Extend control shards doctor.
We will need a small design document for this, before we start implementation.

See #572.

The rationale is to postpone object deletion is some cases an do it manually. We also need some listing capabilities: if blockchain is unavailable, we still want to diagnose what is happening. Metrics are OK, but not verbose. `frostfs-lens` doesn't work unless the service is stopped (it needs exclusive access to the database). Extend `control shards doctor`. We will need a small design document for this, before we start implementation. See #572.

fyrchik added the

frostfs-node

triage

labels 2023-08-07 12:25:25 +00:00

fyrchik added a new dependency 2023-08-07 12:25:41 +00:00

#572 GC improvements

fyrchik added the

discussion

label 2023-08-07 12:27:26 +00:00

fyrchik changed title from ~~Allow doctor to restore/drop objects on a per-container buckets~~ to Allow doctor to restore/drop objects on a per-container buckets

2023-08-07 12:28:02 +00:00

fyrchik added this to the v0.38.0 milestone 2023-08-07 12:32:17 +00:00

fyrchik changed title from ~~Allow doctor to restore/drop objects on a per-container buckets~~ to Allow doctor to restore/drop objects on a per-container basis

2023-12-06 07:56:37 +00:00

fyrchik modified the milestone from v0.38.0 to v0.39.0

2024-02-12 06:37:29 +00:00

fyrchik modified the milestone from v0.39.0 to v0.40.0

2024-05-14 14:12:59 +00:00

fyrchik modified the milestone from v0.40.0 to vNext

2024-05-14 14:13:03 +00:00