DongHyeonkaandClaude Opus 5
2a98ef1090
Cutting TCP 7800 leaves cross-node refresh working (200), confirming sessions travel through PostgreSQL rather than the cluster transport. Logout is the opposite: the database row is deleted but the other node answers from its stale local cache, so the A-0 conclusion that invalidation rides the database is corrected here. Two things the plan did not anticipate: a NetworkPolicy cannot sever an established connection because conntrack accepts it before policy evaluation, and Keycloak reports the partition through its readiness probe so the split node removes itself from the Service. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
18 lines
758 B
Plaintext
18 lines
758 B
Plaintext
=== [대조군] 차단 전 — keycloak-0 로그인 → keycloak-1 에서 refresh ===
|
|
sid tAWs2gCPr6SOcD4jDR9-_CzB
|
|
keycloak-1 에서 refresh: 200
|
|
|
|
=== [기준선 4] JGroups 지표 — 양쪽 노드 ===
|
|
--- K0 (10.42.1.43) ---
|
|
vendor_jgroups_stats_bytes_sent_total 31476.0
|
|
vendor_jgroups_merge3_get_num_merge_events 0.0
|
|
vendor_jgroups_merge3_get_views 0.0
|
|
vendor_jgroups_fd_sock2_get_num_suspected_members 0.0
|
|
vendor_jgroups_nakack2_get_xmit_table_missing_messages 0.0
|
|
--- K1 (10.42.0.35) ---
|
|
vendor_jgroups_merge3_get_views 0.0
|
|
vendor_jgroups_stats_bytes_sent_total 126765.0
|
|
vendor_jgroups_nakack2_get_xmit_table_missing_messages 0.0
|
|
vendor_jgroups_fd_sock2_get_num_suspected_members 0.0
|
|
vendor_jgroups_merge3_get_num_merge_events 0.0
|