John Spray 20d0939b00 control_plane/attachment_service: implement PlacementPolicy::Secondary, configuration updates (#6521) ...

During onboarding, the control plane may attempt ad-hoc creation of a
secondary location to facilitate live migration. This gives us two
problems to solve:
- Accept 'Secondary' mode in /location_config and use it to put the
tenant into secondary mode on some physical pageserver, then pass
through /tenant/xyz/secondary/download requests
- Create tenants with no generation initially, since the initial
`Secondary` mode call will not provide us a generation.

This PR also fixes modification of a tenant's TenantConf during
/location_conf, which was previously ignored, and refines the flow for
config modification:
- avoid bumping generations when the only reason we're reconciling an
attached location is a config change
- increment TenantState.sequence when spawning a reconciler: usually
schedule() does this, but when we do config changes that doesn't happen,
so without this change waiters would think reconciliation was done
immediately. `sequence` is a bit of a murky thing right now, as it's
dual-purposed for tracking waiters, and for checking if an existing
reconciliation is already making updates to our current sequence. I'll
follow up at some point to clarify it's purpose.
- test config modification at the end of onboarding test

2024-03-01 20:25:53 +00:00

..

benches

Remove unused allow's (#6760)

2024-02-14 18:16:05 +00:00

scripts

Upload initdb results to S3 (#5390)

2023-11-23 18:11:52 +00:00

src

control_plane/attachment_service: implement PlacementPolicy::Secondary, configuration updates (#6521)

2024-03-01 20:25:53 +00:00

tests

Remove sync postgres_backend, tidy up its split usage.

2023-03-09 20:45:56 +03:00

Cargo.toml

per-TenantShard read throttling (#6706)

2024-02-16 21:26:59 +01:00