# rolling update dev -> v2 with migration 003 applied under load, 2026-11-07 17:59
# Console output copied verbatim; the JSON of this run was overwritten by the later v2 -> v3 run (rolling-update.json).
# Old replicas: image messenger-lab3-app:dev, built before migrations/003_session_indexes.sql existed
#   (its readiness requires only 001, 002). New image messenger-lab3-app:v2 contains 001-003.
# Command: APP_VERSION=v2 python scripts/failover_series.py --mode action --action scripts/rolling-update.cmd --output evidence/rolling-update.json
running scripts/rolling-update.cmd under load...
{"total": {"seconds": 70.91, "rps_ok": 125.7, "writes_ok": 4458, "reads_ok": 4458, "errors": 0, "p95_ms": 78.1, "instances": {"419aeb0c6c36": 2714, "e90dced210a7": 1695, "a8021c6dc466": 2752, "a2bb8bd69281": 1755}}, "integrity": {"confirmed_writes": 4458, "stored_messages": 4458, "duplicates": 0, "missing_confirmed": 0}}
PASS: action, 4458 confirmed writes, no duplicates, nothing lost
## rolling-update.sh output and metrics
17:59:39 rolling 2 replica(s) to messenger-lab3-app:v2
17:59:48 migrations applied once
17:59:59 new replica(s) UP in LB: a8021c6dc466 ; stopping old e90dced210a7
18:00:05 old e90dced210a7 drained and removed
18:00:17 new replica(s) UP in LB: a2bb8bd69281 a8021c6dc466 ; stopping old 419aeb0c6c36
18:00:24 old 419aeb0c6c36 drained and removed
messenger-lab3-api-3 messenger-lab3-app:v2 Up 33 seconds (healthy)
messenger-lab3-api-4 messenger-lab3-app:v2 Up 15 seconds (healthy)
18:00:24 done; set APP_VERSION=v2 in .env to keep this version on the next compose up
action_seconds 45.73 max_gap 0.097
versions before {'dev': 1001} during {'dev': 3408, 'v2': 2234} after {'v2': 2265}
during {'seconds': 45.73, 'rps_ok': 123.4, 'writes_ok': 2821, 'reads_ok': 2821, 'errors': 0, 'p95_ms': 78.5, 'instances': {'419aeb0c6c36': 2214, 'e90dced210a7': 1194, 'a8021c6dc466': 1615, 'a2bb8bd69281': 619}}
# After 003 was applied at 17:59:48 both dev replicas stayed in rotation until they were replaced
# (17:59:59 and 18:00:17); dev served 3408 successful responses during the action with 0 errors overall,
# i.e. the old build stayed ready and correct on the expanded schema.
