Christian Schwarz 21c444e85f tenant loops: operate on the Arc<Tenant> directly ...

(Instead of going through mgr every iteration.)

The `wait_for_active_tenant` function's `wait` argument could be removed
because it was only used for the loop that waits for the tenant to show
up in the tenants map. Since we're passing the tenant in, we now longer
need to get it from the tenants map.

NB that there's no guarantee that the tenant object is in the tenants map
at the time the background loop function starts running. But the
tenant mgr guarantees that it will be quite soon. See
`tenant_map_insert` way upwards in the call hierarchy for details.

This is prep work to eliminate `subscribe_for_state_updates`.
Which I'm exploring as an alternative to
https://github.com/neondatabase/neon/pull/4291

So, it's part of the https://github.com/orgs/neondatabase/projects/38
    (async get_value_reconstruct_data)

2023-05-22 17:50:08 +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

tenant loops: operate on the Arc<Tenant> directly

2023-05-22 17:50:08 +02:00

Cargo.toml

feat(page_service): read timeouts (#4093)

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