Zone must be named 'local' to match the node

FixKlusterServices
Shipped
August 27, 2026 at 2:26 PM UTC
Author
Kamo
Commit
0787e04

The config.ini was loading correctly and the AMQP URI was right, but every node logged 'no local zone configured, adding default AMQP' and then retried **************** forever. kz_config defaults a node's own zone to 'local'. The [zone] section was named 'us-east-1', so the node could not find its own zone and silently fell back to defaults — a fallback, not an error, which is why it presented as an unreachable broker rather than a configuration mismatch. Multi-region does not rename this: zone identity comes from the node, not from this label.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing