Stateful engine pinned to a single zone
errorstateful-engine-pinned-to-single-zone
A matching engine, coordination service or event store living in exactly one availability zone, with no failover and no replication, is lost with that zone. Everything that depends on it stops with it.
- Severity
- error
- Selects
- every node of kind matching-engine, coordination-service or event-store
- Components in scope
- 26
It looks at every node of kind matching-engine, coordination-service or event-store, and fires when:
- — all of these hold:
- — the node sits inside exactly 1 availability-zone group
- — any of these hold:
- — the node's `failover` is "none"
- — the node's `replicated` is false
- — the node's `replication` is "none"
'{{node.id}}' is pinned to a single availability zone with no failover or replication.Reference designs whose broken twin names this rule in its header. The gate reads the same header, and fails when a rule no design trips.
# yaml-language-server: $schema=../schema/rule.schema.json # A matching engine, coordination service or event store that lives in exactly one # availability zone with no failover or replication is lost with that zone, and everything # that depends on it stops. Tripped by: designs/object-storage.broken.yaml schemaVersion: "1" type: "rule" id: "stateful-engine-pinned-to-single-zone" severity: "error" select: node: kind: ["matching-engine", "coordination-service", "event-store"] when: all: - inGroup: kind: "availability-zone" count: eq: 1 - any: - prop: "failover" equals: "none" - prop: "replicated" equals: false - prop: "replication" equals: "none" message: "'{{node.id}}' is pinned to a single availability zone with no failover or replication."