You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
And swap any uses of `shard_local_cfg()` which occur in the bootstrap
process (before it is marked as `ready`) over to the unsafe accessor.
These uses of potentially stale values are all audited and deemed safe,
due to minimal or no impact on the behavior of the system post bootstrap.
Two other relevant changes in this commit:
* Pulling out `feature_table::setup_metrics()` into its own function,
called after the bootstrap process (in order to properly respect
`shard_local_cfg().disable_{public}_metrics`)
* Updating `storage_resources` to _not_ invoke the `internal::chunks()`
singleton constructor, which would in turn invoke `shard_local_cfg()`.
We use `storage_resources for an early replay of the `kvstore` segments,
so it is fine to use stale configuration values here. However, after
bootstrapping is complete, it is *probably* important to set the
`_append_chunk_size` back to the same value as what `internal::chunks()`
is operating with. We now do so when initializing the storage system in
`wire_up_bootstrap_services()`.
0 commit comments