mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-01 05:37:24 +00:00
pingqiuandClaude Opus 4.6
08dc592d29
Bug: BarrierOK with FlushedLSN == 0 (legacy 1-byte response) was counted as successful sync_all durability even though no authoritative durable progress was established. This allowed a legacy replica to silently pass through the sync_all barrier without proving any LSN was fsynced. Fix (wal_shipper.go): BarrierOK with FlushedLSN == 0 now returns an error instead of nil. Barrier success requires the replica to report a non-zero FlushedLSN proving which LSN was durably persisted. This makes the code match the CP13-3 contract: replicaFlushedLSN is the sole authority for sync_all durability. New test: TestBarrier_LegacyResponseRejectedBySyncAll — proves legacy 1-byte responses don't establish durable authority. Contract review doc updated to reflect the code fix. 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