The level 3 and 4 evidence was taken on24f9d61anda774a2f, before the lab 3 fixes were carried over and before the reconciler. Take all of it again in one series on81dd816, whose application and stand code is the final one: a fresh clone runs the launch block of the report from secrets to reset-data, then one stand from clean volumes gives the smoke, stack, limits, lb-check, failover of each replica and of the upload replica, persistence, S3 outage, S3 privacy, lost-answer retry, upload faults, all stack checks, storage layout and three runs of the upload memory matrix. The three memory runs keep the peak with three slots at 297-345 MiB against 512 MiB at the limit without them, but at 40 uploads of 10 MiB the wait for a slot nears the 8 s request timeout and one run of three gave 7 of 80 a 503. Those timeouts left 67 invisible intents; the record shows the reconciler seeing them as fresh and the sweep removing all of them after the grace period. Message write load is taken with tests/load.py from a container on the edge network: 2 106 RPS, no errors, replicas and PostgreSQL at their CPU limits. The first try from the macOS host is kept as a discarded attempt, it ran out of ephemeral ports while the replicas answered every request. The report gets the defense answers, the load section, the evidence commits, the upload limit order as the pipeline applies it, medians in the track 2 cost table and the proposals over the word limit; the evidence index lists every file with its command and commit. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01V1d3RLHNBBMA6UqBLLJv27
34 lines
1.9 KiB
Plaintext
34 lines
1.9 KiB
Plaintext
date: 2026-10-30T04:29:04Z commit: 81dd816
|
|
$ docker compose --env-file .env config --quiet && echo valid
|
|
valid
|
|
$ docker compose ps --format '{{.Service}} {{.Name}} {{.Status}} {{.Ports}}'
|
|
api mtusi2026lab4-api-1 Up 5 seconds (healthy)
|
|
api mtusi2026lab4-api-2 Up 5 seconds (healthy)
|
|
lb mtusi2026lab4-lb-1 Up 11 seconds (healthy) 127.0.0.1:18084->8080/tcp, 127.0.0.1:24084->8404/tcp
|
|
postgres mtusi2026lab4-postgres-1 Up 11 seconds (healthy)
|
|
s3 mtusi2026lab4-s3-1 Up 11 seconds (healthy)
|
|
valkey mtusi2026lab4-valkey-1 Up 11 seconds (healthy)
|
|
$ docker compose config | grep -c container_name
|
|
0
|
|
$ docker port <каждая реплика api> # реплики не публикуют порт
|
|
0cc3ee358e59: []
|
|
899a952a5a21: []
|
|
$ docker inspect: hostname = X-Instance-Id, сети, лимиты CPU (nano) и памяти
|
|
api 0cc3ee358e59 /mtusi2026lab4-api-1 nets=mtusi2026lab4_backend, cpus=1000000000 mem=536870912 user=10001:10001 ro=true
|
|
api 899a952a5a21 /mtusi2026lab4-api-2 nets=mtusi2026lab4_backend, cpus=1000000000 mem=536870912 user=10001:10001 ro=true
|
|
lb a51c65de79e9 /mtusi2026lab4-lb-1 nets=mtusi2026lab4_backend,mtusi2026lab4_edge, cpus=1000000000 mem=134217728 user=haproxy ro=true
|
|
postgres 54d604398b41 /mtusi2026lab4-postgres-1 nets=mtusi2026lab4_backend, cpus=2000000000 mem=1073741824 user=70:70 ro=false
|
|
s3 89f363c93892 /mtusi2026lab4-s3-1 nets=mtusi2026lab4_backend, cpus=1000000000 mem=536870912 user=rustfs ro=true
|
|
valkey 99365a2af315 /mtusi2026lab4-valkey-1 nets=mtusi2026lab4_backend, cpus=500000000 mem=134217728 user=999:1000 ro=false
|
|
$ curl LB stats: backend api, server status check
|
|
api1 UP L7OK 200
|
|
api2 UP L7OK 200
|
|
BACKEND UP
|
|
$ for i in 1..6: curl -D - http://127.0.0.1:18084/health/live | X-Instance-Id
|
|
x-instance-id: 0cc3ee358e59
|
|
x-instance-id: 899a952a5a21
|
|
x-instance-id: 0cc3ee358e59
|
|
x-instance-id: 899a952a5a21
|
|
x-instance-id: 0cc3ee358e59
|
|
x-instance-id: 899a952a5a21
|