Rongsong Shen
50b976aedc
Add an in-situ NOTICE at the config-upgrade restart site (do_upgrade_config_with_bytes, step 9). Today an upgrade commits the config-change marker, then each member restarts and re-materializes its post-upgrade state by replaying its own pre-upgrade WAL under the NEW config; replay is config-dependent (lost_and_found re-homes orphaned entities), so members can diverge in materialized state (bug-857). The notice records the intended fix — materialize a full entity-bearing snapshot at the marker's (term,lsn) boundary, embed the new config, and install the SAME snapshot on every member via snapshot_transfer_s — and its hard dependency on entity-bearing-snapshots. Comment-only; anchors to .kiro/specs/config-upgrade-snapshot/. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MSxwb2Xt5F84ATgiAZnH8V |
||
|---|---|---|
| .. | ||
| autoscaler | ||
| controller | ||
| docs | ||
| frontend | ||
| include | ||
| lib | ||
| nixSupport | ||
| scheduler | ||
| schema | ||
| tools | ||
| worker | ||
| build | ||
| flake.lock | ||
| flake.nix | ||
| meson.build | ||
| meson.options | ||