mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-20 13:30:46 +02:00
pingqiu
88cff6145c
Architect approved Option B 2026-04-27: absorb the hardware-revealed gap into G5-5C as Batch #7 instead of carrying to G5-5D. §1.I scope: - core/host/volume/peer_command_executor.go (NEW, ~120 LOC) - core/host/volume/peer_adapter_registry.go (NEW, ~100 LOC) - core/replication/volume.go ConfigurePeerLifecycleHook (~30 LOC) - core/host/volume/probe_loop_wiring.go router signature (~20 net) - cmd/blockvolume/main.go registry wire-up (~20 net) - ~10 new tests, ~250 LOC test code INV INV-G5-5C-PER-PEER-ADAPTER-PER-PEER-ENGINE absorbed back in-batch (was previously deferred to G5-5D in pre-architect-ruling draft). Pass criterion unchanged: m01 verify_restart_catchup GREEN within 30s deadline; #1-#3 regression GREEN in the same run. §close updated: ceremony waits for Batch #7 land + hardware re-run; G5-5C closes at full L4 in one shot.
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