Christian Schwarz 3ec52088dd eviction_task: tracing::instrument the imitate-access calls (#4180) ...

Currently, if we unexpectly download from the eviction task, the log
lines look like what we have in
https://github.com/neondatabase/neon/issues/4154

```
2023-05-04T14:42:57.586772Z  WARN eviction_task{tenant_id=$TENANT timeline_id=$TIMELINE}:eviction_iteration{policy_kind="LayerAccessThreshold"}: unexpectedly on-demand downloading remote layer remote $TIMELINE/000000067F000032AC0000400C00FFFFFFFF-000000067F000032AC000040140000000008__0000000001696070-0000000003DC76E9 for task kind Eviction
```

We know these are caused by the imitate accesses.
But we don't know which one (my bet is on update_gc_info).

I didn't want to pollute the other tasks' logs with the additional
spans, so, using `.instrument()` when we call non-eviction-task code.

refs https://github.com/neondatabase/neon/issues/4154

2023-05-09 18:16:22 +02:00

..

benches

revert: "Add check for duplicates of generated image layers" (#4104)

2023-04-28 17:20:18 +03:00

fixtures

walredo: simple tests and bench updates (#3045)

2023-01-16 18:24:45 +02:00

src

eviction_task: tracing::instrument the imitate-access calls (#4180)

2023-05-09 18:16:22 +02:00

Cargo.toml

feat(page_service): read timeouts (#4093)

2023-04-27 17:55:35 +00:00