Christian Schwarz a48b23d777 fix(startup + remote_timeline_client): no-op deletion ops scheduled during startup (#6825) ...

Before this PR, if remote storage is configured, `load_layer_map`'s call
to `RemoteTimelineClient::schedule_layer_file_deletion` would schedule
an empty UploadOp::Delete for each timeline.

It's jsut CPU overhead, no actual interaction with deletion queue
on-disk state or S3, as far as I can tell.

However, it shows up in the "RemoteTimelineClient calls started
metrics", which I'm refining in an orthogonal PR.

2024-02-20 14:06:25 +01:00

..

benches

bench_walredo: use tokio multi-threaded runtime (#6743)

2024-02-16 16:31:54 +01:00

client

storage controller: improved handling of node availability on restart (#6658)

2024-02-08 18:00:53 +00:00

ctl

live-reconfigurable virtual_file::IoEngine (#6552)

2024-02-07 17:47:55 +00:00

pagebench

per-TenantShard read throttling (#6706)

2024-02-16 21:26:59 +01:00

src

fix(startup + remote_timeline_client): no-op deletion ops scheduled during startup (#6825)

2024-02-20 14:06:25 +01:00

test_data

Add walingest test (#5892)

2023-11-28 12:50:53 -05:00

Cargo.toml

per-TenantShard read throttling (#6706)

2024-02-16 21:26:59 +01:00