mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-20 13:30:46 +02:00
pingqiuandClaude Opus 4.7
822c588d08
§11.6 startRebuildDualLane row updated with landed-2026-04-30 commit receipts on g7-redo/wal-shipper-impl: - e354813 fix(transport): unify replicaID in startRebuildDualLane - e5a8763 fix(test): align component cluster harness to replica-%d Module-wide go test green (25 packages). Phase 0 closed. §11.7 added — heavy integration proof matrix on the manager-assembled session (BlockExecutor + PrimaryBridge + RecoverySink + recovery.Sender + resident WalShipper + PeerShipCoordinator under unified replicaID). Three pillars: (1) WalShipper backlog/realtime modes, (2) dual-line execution + writeMu interleave, (3) receiver convergence. Order: Phase 0 + SHA receipt → C3 fault-injection → widen matrix → T2/T7 hardware soak. Stop rule: failure at assembled-session layer fixes algorithm/wiring before Phase 1 attempt binder. Revision rows v0.7 + v0.8 record the §11.6 + §11.7 deltas. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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