forked from mtusi2026/mtusi2026lab3
30 lines
1.4 KiB
Plaintext
30 lines
1.4 KiB
Plaintext
# failures: Redis and PostgreSQL outages via the balancer
|
|
# date: 2026-10-14 20:27:54, commit: 0ab3a34 + uncommitted changes
|
|
# command: python.exe student-tests/test_failures.py
|
|
# exit code: 0, 47.0 s
|
|
|
|
stopping redis
|
|
/health/live -> 200, /health/ready -> 503 (3297 ms)
|
|
valid token: GET /users/me -> 503 unavailable (3281 ms), session cannot be checked
|
|
unknown token -> 503, not 200: nobody is trusted without a check
|
|
no token -> 401
|
|
login -> 503: there is nowhere to store the session
|
|
registration -> 201: it needs only PostgreSQL
|
|
starting redis
|
|
after start: the old token works, confirmed messages are in place
|
|
PASS: Redis outage gives 503 and does not let anyone in without a session check
|
|
killing redis with SIGKILL (docker compose kill redis): no graceful shutdown
|
|
right after the crash: GET /users/me -> 503
|
|
starting redis
|
|
after start: the session issued before the crash still works (AOF, appendfsync always)
|
|
PASS: sessions survive a Redis crash, not only a clean restart
|
|
stopping postgres
|
|
/health/live -> 200, /health/ready -> 503 (1015 ms)
|
|
valid token: users/me, chats, history, new message -> 503 unavailable, no details
|
|
no token -> 401, unknown token -> 401: anonymous users are not let in
|
|
login -> 503, registration -> 503
|
|
starting postgres
|
|
after start: the old token works, confirmed messages are in place
|
|
PASS: PostgreSQL outage gives limited 503 errors and keeps anonymous users out
|
|
3 passed, 0 failed
|