DongHyeonkaandClaude Opus 5
f45a2a2aaa
Stopping Redis returns HTTP 000 rather than an error because the client waits on reconnect, and the pod keeps serving traffic because the redis health indicator is not in the readiness group even though /actuator/health returns 503. That is the mirror image of A-2, where Keycloak put its database check in readiness and the pods left the Service. Turning on AOF with config set created the appendonlydir and still lost everything on pod deletion, because /data was the container filesystem; adding a PVC makes the same setting work. Volume first, persistence setting second. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
40 lines
1.2 KiB
Plaintext
40 lines
1.2 KiB
Plaintext
=== 복구 ===
|
|
deployment.apps/redis scaled
|
|
deployment "redis" successfully rolled out
|
|
/actuator/health HTTP 200
|
|
/bff/token-boundary HTTP 302
|
|
BFF 재시작 필요했나: 0,0 회 재시작
|
|
|
|
=== ② 영속화 — 지금 설정으로 재시작하면 무엇이 남는가 ===
|
|
키 심음: before-restart
|
|
dbsize: 4
|
|
|
|
--- AOF 를 켜고 다시 심는다 (영속화가 켜져 있으면 살아남는가) ---
|
|
appendonly yes
|
|
total 12
|
|
drwxr-xr-x 3 redis redis 4096 Sep 4 05:26 .
|
|
drwxr-xr-x 1 root root 4096 Sep 4 05:26 ..
|
|
drwx------ 2 redis redis 4096 Sep 4 05:26 appendonlydir
|
|
|
|
--- 파드를 지운다 ---
|
|
deployment "redis" successfully rolled out
|
|
재기동 후:
|
|
dbsize: 0
|
|
b5:probe
|
|
b5:aof
|
|
appendonly no
|
|
persistentvolumeclaim/redis-data created
|
|
deployment.apps/redis configured
|
|
deployment "redis" successfully rolled out
|
|
|
|
=== 영속 볼륨 위에서 다시 시험 ===
|
|
appendonly yes
|
|
키 심음: written-on-pvc
|
|
sed: -e expression #1, char 8: unknown option to 's'
|
|
|
|
--- 파드를 지운다 ---
|
|
deployment "redis" successfully rolled out
|
|
재기동 후:
|
|
dbsize: 1
|
|
b5:pvc written-on-pvc
|