Skip to content

Commit 940ef66

Browse files
committed
docs: call out single-replica / no-HA limitation in README Status
The HA limitation is documented in TODO.md as out-of-scope for the initial release; this surfaces it on the public README so first-time operators know to design around single-replica before they design into it. Mentions both the cancel-routing constraint and the chart's `replicaCount: 1` default.
1 parent 59df840 commit 940ef66

1 file changed

Lines changed: 6 additions & 0 deletions

File tree

README.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,12 @@ What is intentionally not implemented for now:
2020
- Per-IP rate limiting (only a global concurrent-connection cap).
2121
- Cancel of statements in a multi-statement batch other than the
2222
most-recently-submitted one.
23+
- Multi-replica / high-availability deployment. The cancel registry
24+
and per-connection state are in-memory; running more than one
25+
replica behind a load balancer needs sticky-by-connection routing
26+
AND requires the PG `CancelRequest` to land on the same replica as
27+
the original connection. The Helm chart defaults to `replicaCount:
28+
1` and the Service is the single coordination point.
2329

2430
## Build
2531

0 commit comments

Comments
 (0)