John Spray 1ab0cfc8cb pageserver: add sharding metadata to LocationConf (#5932) ...

## Problem

The TenantShardId in API URLs is sufficient to uniquely identify a
tenant shard, but not for it to function: it also needs to know its full
sharding configuration (stripe size, layout version) in order to map
keys to shards.

## Summary of changes

- Introduce ShardIdentity: this is the superset of ShardIndex (#5924 )
that is required for translating keys to shard numbers.
- Include ShardIdentity as an optional attribute of LocationConf
- Extend the public `LocationConfig` API structure with a flat
representation of shard attributes.

The net result is that at the point we construct a `Tenant`, we have a
`ShardIdentity` (inside LocationConf). This enables the next steps to
actually use the ShardIdentity to split WAL and validate that page
service requires are reaching the correct shard.

2023-11-28 13:14:51 +00:00

..

src

pageserver: add sharding metadata to LocationConf (#5932)

2023-11-28 13:14:51 +00:00

Cargo.toml

pageserver: add sharding metadata to LocationConf (#5932)

2023-11-28 13:14:51 +00:00