docs: A-5 — a one-way block heals itself and a full split still leaves one node serving

Browse Source

Three injections failed first: kube-router keeps reinserting its chain above a hand-placed FORWARD rule, the JGroups connection direction had reversed since A-1, and only the raw table runs ahead of conntrack. Each failure looked like nothing happening.

Blocking one direction never partitioned the cluster because JGroups reconnected the other way before failure detection fired. Blocking both produced a real split brain with two coordinators in JGROUPS_PING, yet only the non-coordinator node reported DOWN, so the Service kept an endpoint and the front door stayed at 200. That answers the question A-1 left open.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

...

This commit is contained in:

DongHyeonka

2026-09-04 13:12:04 +09:00

co-authored by Claude Opus 5

parent d0666c5ba0

commit 2fa77a899e

14 changed files with 754 additions and 0 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

docs/evidence/a5-asymmetric-partition/02-injection-verify.txt