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>
26 lines
900 B
Plaintext
26 lines
900 B
Plaintext
=== 주입: postgres(10.42.1.76) 가 보내는 패킷만 200ms 지연 (kc-lab-2 eth0) ===
|
|
prio qdisc 로 밴드를 나누고, u32 필터로 출발지 IP 가 postgres 인 것만 3번 밴드로 보낸다
|
|
Cannot find device "eth0"
|
|
Cannot find device "eth0"
|
|
적용완료
|
|
Cannot find device "eth0"
|
|
Cannot find device "eth0"
|
|
주입: 13:14:55
|
|
|
|
=== [검증] 지연이 실제로 걸렸는가 — 두 노드 비교 ===
|
|
keycloak-0 평균 43 ms 최대 64 ms
|
|
keycloak-1 평균 47 ms 최대 70 ms
|
|
|
|
=== 커넥션 풀 상태 ===
|
|
--- keycloak-0 ---
|
|
agroal_blocking_time_max_milliseconds 102.0
|
|
agroal_active_count 0.0
|
|
agroal_awaiting_count 0.0
|
|
agroal_blocking_time_average_milliseconds 0.0
|
|
agroal_available_count 2.0
|
|
agroal_blocking_time_max_milliseconds 164.0
|
|
agroal_active_count 0.0
|
|
agroal_awaiting_count 0.0
|
|
agroal_blocking_time_average_milliseconds 0.0
|
|
agroal_available_count 2.0
|