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>
26 lines
1.0 KiB
Plaintext
26 lines
1.0 KiB
Plaintext
=== ① Redis 정지 ===
|
|
정지: 14:26:30
|
|
deployment.apps/redis scaled
|
|
삭제 완료
|
|
|
|
=== 로그인한 사용자의 다음 요청은 어떻게 되는가 ===
|
|
/ HTTP 200
|
|
/bff/token-boundary HTTP 000
|
|
/actuator/health HTTP 503
|
|
--- token-boundary 응답 본문 ---
|
|
|
|
|
|
=== 파드 상태 — readiness 가 Redis 를 보는가 ===
|
|
bff-555df79c97-6j86w 1/1 Running 0 17m
|
|
bff-555df79c97-vgg6g 1/1 Running 0 16m
|
|
|
|
=== health 상세 ===
|
|
|
|
|
|
=== BFF 로그 ===
|
|
at java.base/sun.nio.ch.Net.pollConnect(Native Method) ~[na:na]
|
|
at java.base/sun.nio.ch.Net.pollConnectNow(Unknown Source) ~[na:na]
|
|
at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(Unknown Source) ~[na:na]
|
|
at io.netty.channel.socket.nio.NioSocketChannel.doFinishConnect(NioSocketChannel.java:336) ~[netty-transport-4.1.135.Final.jar!/:4.1.135.Final]
|
|
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:339) ~[netty-transport-4.1.135.Final.jar!/:4.1.135.Final]
|