mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-20 13:30:46 +02:00
m01 hardware run 4 at seaweed_block@712cbc47 (with Batch #7 per-peer adapter wiring) — full results: #1 verify_cluster_ready ✅ GREEN #2 verify_byte_equal ✅ GREEN #3 verify_network_catchup ✅ GREEN (9s) #4 verify_restart_catchup ✅ GREEN (9s) ← Batch #7 unblocked #5 verify_race_stress (×10) ✅ GREEN #6 verify_full_suite ✅ GREEN §close updated: - Header: closes at L4 Replicated IO with peer-restart resilience. - §close.evidence hardware-pin row table: run 4 results. - Earlier-runs row table preserved for artifact retention (run 2 port-release race; run 3 per-peer adapter gap; both root-caused and fixed). - §close.findings 'per-peer adapter gap' marked RESOLVED by Batch #7. - §close.deltas: forward-carry to G5-5D dropped (absorbed in-batch). - §close.forward-carries: G5-5D removed; only G5-5 deferred ledger pointers + G5-2/G5-3/future master observability remain. - architect-review-checklist: scope truth, engine impact, product level all updated to reflect L4 reached on hardware. INV-G5-5C-PER-PEER-ADAPTER-PER-PEER-ENGINE inscribed at this close (no longer deferred). Awaiting QA evidence verification + architect single-sign per v3-batch-process.md §5 + §8C.2.
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