test(raft-ha-core-safety): RED — snapshot install does not reconcile (term,lsn) boundary (task 3.1)
ha_handle_snapshot_chunk/persist_load_snapshot advance checkpoint_lsn, current_lsn, and applied_lsn on snapshot install but never touch the per-LSN term index, so a divergent pre-snapshot entry's stale local term survives the install unreconciled. New test proves the gap (Expected 7 Was 3); fix lands in task 3.2.
This commit is contained in:
parent
02dfedfbe8
commit
21858faba4
2 changed files with 120 additions and 1 deletions
|
|
@ -67,7 +67,7 @@
|
|||
- _Depends: 2.2, 2.3_
|
||||
|
||||
- [ ] 3. Snapshot-boundary reconciliation
|
||||
- [ ] 3.1 RED: snapshot post-install reconcile test
|
||||
- [x] 3.1 RED: snapshot post-install reconcile test
|
||||
- Add a case where a divergent pre-snapshot entry must be reconciled against the installed checkpoint's `(term, lsn)` boundary (today snapshot install sets applied-lsn without a `(term, lsn)` reconcile)
|
||||
- Observable completion: the case FAILS on the baseline because no `(term, lsn)` reconcile occurs at the snapshot boundary
|
||||
- _Requirements: 3.1, 5.1_
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue