mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-05-19 08:11:29 +00:00
600dac6029
Baseline report (phase-13-cp1-baseline.md) from running 44 existing replication-gap tests on current code with zero protocol changes: 37 PASS / 4 FAIL / 3 PASS* 4 FAILs expose real gaps: - ReconnectUsesHandshakeNotBootstrap: degraded shipper doesn't catch up (CP13-5) - CatchupMultipleDisconnects: repeated reconnect cycles don't recover (CP13-5) - NeedsRebuildBlocksAllPaths: stays Degraded after large gap (CP13-5+7) - CatchupDoesNotOverwriteNewerData: catch-up fails at barrier (CP13-5) 3 PASS* are witness-only (pass but don't prove the property): - Bug3_ReplicaAddr: documents gap, not fix (CP13-2) - GapBeyondRetainedWal: asserts barrier failure, not NeedsRebuild (CP13-7) - MaxBytesTriggersNeedsRebuild: logs "not implemented" (CP13-6) No protocol code changed. Baseline is test-first evidence only. Co-Authored-By: Claude Opus 4.6 (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