Random channel placement under heavy-tail traffic

errorshared-host-per-channel-without-isolation

With heavy-tail traffic a few channels carry most of the load. Assigning channels at random lands those hot channels on arbitrary hosts, and every tenant sharing a host suffers for it.

Severity
error
Selects
every node of kind realtime-gateway
Components in scope
20
What it checks

It looks at every node of kind realtime-gateway, and fires when:

  • — all of these hold:
  • — the node's `channelAssignment` is "random"
  • — the design requirement `traffic.skew` is "heavy-tail"
Message
Realtime gateway '{{node.id}}' assigns channels randomly while the design declares heavy-tail traffic. Hot channels will degrade unrelated tenants on the same host.

{{node.id}} style paths are filled in from the node, the edge or the design the finding is about.

Applies to · 20 components
Tripped by · 4

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.

Source
# yaml-language-server: $schema=../schema/rule.schema.json
# With heavy-tail traffic a few channels carry most of the load. Random channel
# assignment lands those hot channels on arbitrary hosts and every tenant sharing that
# host suffers. Assign channels by hash or sticky placement so hot spots are predictable
# and movable.
# Tripped by: designs/slack-messaging.broken.yaml
schemaVersion: "1"
type: "rule"
id: "shared-host-per-channel-without-isolation"
severity: "error"
select:
  node:
    kind: "realtime-gateway"
when:
  all:
    - prop: "channelAssignment"
      equals: "random"
    - requirement: "traffic.skew"
      equals: "heavy-tail"
message: "Realtime gateway '{{node.id}}' assigns channels randomly while the design declares heavy-tail traffic. Hot channels will degrade unrelated tenants on the same host."

The same page as markdown, for an agent: /catalogue/rules/shared-host-per-channel-without-isolation.md