...
- Workspace list
- Possibly users
- User or workspace secrets
- (soft) Issued security tokens
- (soft) Logical host naming
Assume 16K machines.
Authentication data:
(application id, secret)
Size: Negligible
Churn: Negligible
Logical host mapping:
(logical host address, network host address/service)
Size: 16 bytes * 16K machines = 256K
Churn: Low (2 entries per 15 minutes)
Machine configuration and placement information:
(network host address, rack, machine configuration)
About the same properties as above, might be able to join the two depending on whether we wrap backup together with masters or whether we want independent services.
Tablet Mapping:
(logical host address, workspace, table/index, start id, end id)
Size: 640K/tablet/server
Churn: Dependent on reconfiguration. Could be more or less frequent than crashes.
Unallocated machines:
(network host address)
Size: Negligible
Churn: Similar to logical host mappings