John Spray d066dad84b pageserver: prioritize activation of tenants with client requests (#6112) ...

## Problem

During startup, a client request might have to wait a long time while
the system is busy initializing all the attached tenants, even though
most of the attached tenants probably don't have any client requests to
service, and could wait a bit.

## Summary of changes

- Add a semaphore to limit how many Tenant::spawn()s may concurrently do
I/O to attach their tenant (i.e. read indices from remote storage, scan
local layer files, etc).
- Add Tenant::activate_now, a hook for kicking a tenant in its spawn()
method to skip waiting for the warmup semaphore
- For tenants that attached via warmup semaphore units, wait for logical
size calculation to complete before dropping the warmup units
- Set Tenant::activate_now in `get_active_tenant_with_timeout` (the page
service's path for getting a reference to a tenant).
- Wait for tenant activation in HTTP handlers for timeline creation and
deletion: like page service requests, these require an active tenant and
should prioritize activation if called.

2023-12-15 20:37:47 +00:00

..

benches

pageserver: refactor TenantId to TenantShardId in Tenant & Timeline (#5957)

2023-11-29 14:52:35 +00:00

client

add a Rust client for Pageserver management API (#6127)

2023-12-15 18:33:45 +01:00

ctl

pagectl: add subcommand to rewrite layer file summary (#5933)

2023-11-30 11:34:30 +00:00

src

pageserver: prioritize activation of tenants with client requests (#6112)

2023-12-15 20:37:47 +00:00

test_data

Add walingest test (#5892)

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

Cargo.toml

pageserver: heatmap uploads (#6050)

2023-12-14 13:09:24 +00:00