John Spray 1b41db8bdd pageserver: enable setting stripe size inline with split request. (#7093) ...

## Summary

- Currently we can set stripe size at tenant creation, but it doesn't
mean anything until we have multiple shards
- When onboarding an existing tenant, it will always get a default shard
stripe size, so we would like to be able to pick the actual stripe size
at the point we split.

## Why do this inline with a split?

The alternative to this change would be to have a separate endpoint on
the storage controller for setting the stripe size on a tenant, and only
permit writes to that endpoint when the tenant has only a single shard.
That would work, but be a little bit more work for a client, and not
appreciably simpler (instead of having a special argument to the split
functions, we'd have a special separate endpoint, and a requirement that
the controller must sync its config down to the pageserver before
calling the split API). Either approach would work, but this one feels a
bit more robust end-to-end: the split API is the _very last moment_ that
the stripe size is mutable, so if we aim to set it before splitting, it
makes sense to do it as part of the same operation.

2024-03-12 20:41:08 +00:00

..

src

pageserver: enable setting stripe size inline with split request. (#7093)

2024-03-12 20:41:08 +00:00

Cargo.toml

feat: bare-bones /v1/utilization (#6831)

2024-02-22 13:58:59 +02:00