mirror of
https://github.com/seaweedfs/seaweedfs.git
synced 2026-10-12 09:17:44 +02:00
pingqiuandClaude Opus 4.6
d7cd415714
One named workload validation package for RF=2 sync_all: - Scenario: cp13-8-real-workload-validation.yaml (6 phases) - ext4 proof: write 200 files → failover → fsck + file count + md5sum diff - pgbench proof: TPC-B on promoted replica (database durability) - Disturbance: one bounded failover (kill primary, promote replica) Workload envelope doc: phase-13-cp8-workload-validation.md - Named topology, transport, workloads, disturbance, exclusions - Pass criteria: fsck passes, 200 files, checksums match, pgbench TPS > 0 - Maps each pass criterion to accepted CP13-1..7 semantics - Explicit non-claims: not rollout approval, not NVMe, not soak, not CP13-9 Reuses existing infrastructure: - cp85-db-ext4-fsck.yaml pattern (extended with checksums + pgbench) - benchmark-pgbench.yaml actions (pgbench_init/pgbench_run) Must run on real hardware (m01/M02). Cannot run in unit test harness. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Phase Dev
Use this directory for private phase development notes.
Phase Protocol
Each phase should use this file set:
phase-01.md- plan
- scope
- progress
- active tasks
- exit criteria
phase-01-log.md- dated development log
- experiments
- test runs
- failures and findings
phase-01-decisions.md- key algorithm decisions
- tradeoffs
- rejected alternatives
Suggested naming pattern:
phase-01.mdphase-01-log.mdphase-01-decisions.mdphase-02.mdphase-02-log.mdphase-02-decisions.md
Rule of use:
- if it is what we are doing ->
phase-xx.md - if it is what happened ->
phase-xx-log.md - if it is why we chose something ->
phase-xx-decisions.md