The controller takes one announcement at a time #173

2026-09-30T19:37:55Z

jschoubben commented

2026-09-30 19:37:55 +00:00

novox/hq issue 175. The controller's events consumer had no bound on outstanding deliveries: the client was handed every waiting announcement, the heartbeat kept only the one being built alive, the rest timed out and came back, and a merge that came back rebuilt builder and route-proxy again — five times over tonight. MaxAckPending: 1 on that consumer; the existing consumer is updated in place by the assertion at start. Merging at once: it is what is making the mesh slow.

novox/hq issue 175. The controller's events consumer had no bound on outstanding deliveries: the client was handed every waiting announcement, the heartbeat kept only the one being built alive, the rest timed out and came back, and a merge that came back rebuilt builder and route-proxy again — five times over tonight. `MaxAckPending: 1` on that consumer; the existing consumer is updated in place by the assertion at start. Merging at once: it is what is making the mesh slow.

jschoubben added 1 commit 2026-09-30 19:37:55 +00:00

The controller takes one announcement at a time 474f68b34c

A merge's handler builds for minutes and keeps its own delivery alive; the announcements handed over
behind it timed out on the client and came back, and a merge that came back rebuilt what it had just
built, five times over (novox/hq issue 175). MaxAckPending 1 on the events consumer: the server holds
the rest.

jschoubben merged commit af31315a5f into main

2026-09-30 19:37:57 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#173