mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-09-10 10:06:12 +00:00
pingqiu
74e92b974d
Architect single-signed §1-§6 at seaweedfs@ba7bd0ba4 2026-04-27 with: - Option B trigger source (primary-side degraded-peer probe loop) - Probe loop placement = core/replication/ owned by ReplicationVolume - Master protocol unchanged - §1.H code-start audit gate before code This commit: 1. Records the single-sign in the doc header. 2. Adds a §1 scope-rule one-liner near the top so future readers find the architect-bound boundary without re-reading the v0.1→v0.5 trail: "master owns identity/topology; primary+engine own data recovery; the protocol aligns the two via (PeerSetGeneration, epoch, EndpointVersion) fences." §1.A already bound Option B in v0.4; no flip needed there. No design change. §1.H audit is the next sw step before any production code.
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