DongHyeonkaandClaude Opus 5
dba0c3975c
Nine database round trips per login multiply the injected delay to 1.9 seconds, and connection pool queueing multiplies it again under twenty concurrent requests. The readiness probe joins the same queue and times out, so the node leaves the load balancer and pushes its load onto the one still standing. Two injections missed first: the guest interface is enp1s0 rather than eth0, and a filter on it can never match a pod IP because flannel has already encapsulated the packet. The delay has to go on flannel.1, before encapsulation. The predicted rise in optimistic lock conflicts did not happen, because logins insert new rows rather than contending for one. That belongs to B-3. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
13 lines
364 B
Plaintext
13 lines
364 B
Plaintext
=== 지연 해제 ===
|
|
해제완료
|
|
qdisc noqueue 0: root refcnt 2
|
|
|
|
=== 회복 확인 ===
|
|
keycloak-0 평균 43 ms
|
|
keycloak-1 평균 51 ms
|
|
keycloak-0 1/1 Running 0 61m
|
|
keycloak-1 1/1 Running 1 (52m ago) 3h24m
|
|
|
|
=== 낙관적 락 충돌이 늘었는가 — 지연 중 로그 ===
|
|
관련 로그 줄수: 0
|