John Spray 107f535294 storage controller: fix handing of tenants with no timelines during scheduling optimization (#7673) ...

## Problem

Storage controller was using a zero layer count in SecondaryProgress as
a proxy for "not initialized". However, in tenants with zero timelines
(a legitimate state), the layer count remains zero forever.

This caused https://github.com/neondatabase/neon/pull/7583 to
destabilize the storage controller scale test, which creates lots of
tenants, some of which don't get any timelines.

## Summary of changes

- Use a None mtime instead of zero layer count to determine if a
SecondaryProgress should be ignored.
- Adjust the test to use a shorter heatmap upload period to let it
proceed faster while waiting for scheduling optimizations to complete.

2024-05-09 12:33:09 +01:00

..

migrations

Clean up 'attachment service' names to storage controller (#7326)

2024-04-05 16:18:00 +01:00

src

storage controller: fix handing of tenants with no timelines during scheduling optimization (#7673)

2024-05-09 12:33:09 +01:00

Cargo.toml

Store operation identifier in IdLockMap on exclusive lock (#7397)

2024-05-03 09:38:19 +01:00