John Spray 14853a3284 storcon: don't take any Service locks in /status and /ready (#9944) ...

## Problem

We saw unexpected container terminations when running in k8s with with
small CPU resource requests.

The /status and /ready handlers called `maybe_forward`, which always
takes the lock on Service::inner.

If there is a lot of writer lock contention, and the container is
starved of CPU, this increases the likelihood that we will get killed by
the kubelet.

It isn't certain that this was a cause of issues, but it is a potential
source that we can eliminate.

## Summary of changes

- Revise logic to return immediately if the URL is in the non-forwarded
list, rather than calling maybe_forward

2024-12-01 18:09:58 +00:00

..

client

Remove unnecessary dependencies (#9000)

2024-09-17 17:55:45 +03:00

migrations

storcon: track preferred AZ for each tenant shard (#8937)

2024-09-06 13:11:17 +01:00

src

storcon: don't take any Service locks in /status and /ready (#9944)

2024-12-01 18:09:58 +00:00

Cargo.toml

Rename hyper 1.0 to hyper and hyper 0.14 to hyper0 (#9254)

2024-10-03 16:33:43 +02:00