Joonas Koivunen fb66a3dd85 fix: ResidentLayer::load_keys should not create INFO level span (#7174) ...

Since #6115 with more often used get_value_reconstruct_data and friends,
we should not have needless INFO level span creation near hot paths. In
our prod configuration, INFO spans are always created, but in practice,
very rarely anything at INFO level is logged underneath.
`ResidentLayer::load_keys` is only used during compaction so it is not
that hot, but this aligns the access paths and their span usage.

PR changes the span level to debug to align with others, and adds the
layer name to the error which was missing.

Split off from #7030.

2024-03-20 15:08:03 +01:00

..

benches

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

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

client

pageserver, controller: improve secondary download APIs for large shards (#7131)

2024-03-15 19:45:58 +00:00

compaction

Minor improvements to tiered compaction (#7020)

2024-03-05 16:26:51 +01:00

ctl

pageserver: optimise disk io for vectored get (#6780)

2024-02-28 12:06:00 +00:00

pagebench

tokio-epoll-uring: use it for on-demand downloads (#6992)

2024-03-15 18:57:05 +00:00

src

fix: ResidentLayer::load_keys should not create INFO level span (#7174)

2024-03-20 15:08:03 +01:00

test_data

Add walingest test (#5892)

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

Cargo.toml

build: make procfs linux only dependency (#7156)

2024-03-18 09:28:45 +00:00