mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-21 07:24:25 +00:00
pingqiu
5069e74445
Per architect ruling 2026-04-28 on QA's expanded scenario report: - A (capacity): 🐛 → ✅ already-fixed at seaweed_block@a250b52, INV inscribed. - B (500 random LBAs over 65536-LBA volume): ✅ GREEN. Confidence bump on dirty-map skew + ship order under random write pattern. - C (kill replica mid-write-storm + restart + 200 LBAs converge): ✅ GREEN. Highest-signal recovery scenario in the expansion; validates G5-5C peer-recovery trigger under load. - D (5000-LBA sustained write → WALRecycled past replica LSN): 🐛 boundary finding. Architect: G6 territory, not G5-5C reopener. Catch-up requires WAL retention; rebuild path is for gap-beyond- WAL. Engine has dispatch-branch tests (Batch 4); runtime escalation path under sustained pressure is G6 acceptance scope. Doc updates: - New §close.appendix table with all 4 scenario rows + dispositions. - Semantic clarification on D — catch-up vs WAL recycle vs rebuild. - §close.forward-carries gets a NEW G6 entry with backlog ticket text, evidence pointer, cross-reference to INV-G5-5C-PROBE-BEFORE- CATCHUP, and explicit non-reopener rationale. - Logs + scenario script paths recorded for QA continuity. §close substance unchanged: G5-5C gate (verify_restart_catchup GREEN within 30 s) was met on the canonical case at seaweed_block@712cbc47 + capacity addendum at a250b52. B/C are strengthening, not gating; D is forward-carry. Awaiting architect final §close single-sign on this tree.
sw-block
Private WAL V2 and standalone block-service workspace.
Purpose:
- keep WAL V2 design/prototype work isolated from WAL V1 production code in
weed/storage/blockvol - allow private design notes and experiments to evolve without polluting V1 delivery paths
- keep the future standalone
sw-blockproduct structure clean enough to split into a separate repo later if needed
Suggested layout:
design/: shared V2 design docsprototype/: code prototypes and experiments.private/: private notes, phase development, roadmap, and non-public working material
Repository direction:
- current state:
sw-block/is an isolated workspace insideseaweedfs - likely future state:
sw-blockbecomes a standalone sibling repo/product - design and prototype structure should therefore stay product-oriented and not depend on SeaweedFS-specific paths