Replicated
A replicated cluster has three nodes, each with its own copy of the data. When one stops, the others keep serving and the engine moves the work to them in seconds, with no acknowledged message lost:
- Kafka: topics have 3 copies by default and
min.insync.replicas=2. A producer usingacks=allgets an acknowledgement once two copies have the write. Partition leadership moves to a node still serving. - RabbitMQ: quorum queues and streams have 3 members. A publisher using publisher confirms gets a confirm once a majority has the message. A queue’s leader moves to a node still serving.
The cluster is degraded while a node is out of service, and returns to available by itself.
A topic an app created with fewer copies, and a classic queue, are on fewer nodes, as the app asked.
Single node
A single-node cluster has one node. When it stops, it’s recovering until it’s back, with its data.
Grow to replicated
ezgh hosted-queues clusters grow hqc_4k2m9x0a7qpe --waitIn the console, it’s Grow to replicated on the cluster’s page. The cluster is modifying and serves
meanwhile. Growing adds nodes 1 and 2, then:
- Kafka: gives Kafka’s internal topics, and topics created through EZGH without a replication
factor, 3 copies, then sets the cluster’s defaults to 3 copies and
min.insync.replicas=2. Topics an app created keep their copies, unless you also ask for them: Also give app-created topics 3 copies in the console’s Grow dialog (unchecked by default), or--raise-app-topics. - RabbitMQ: grows every quorum queue and stream to 3 members.
Classic queues, and the app-created topics you didn’t raise, stay as they are; the operation’s result counts them. Growing can’t be undone: a replicated cluster can’t go back to a single node.
Raise topics to 3 copies
A topic keeps the replication factor it was created with. Apps such as Sentry’s Snuba and PostHog create their topics with one copy, which is unavailable while its node is out of service. To give every topic with fewer than 3 copies three, while the cluster serves:
ezgh hosted-queues clusters raise-replication hqc_4k2m9x0a7qpe --waitIn the console, it’s Raise to 3 copies on the Topics tab, shown when a topic has fewer copies
than the cluster has nodes. To raise one topic, use ezgh hosted-queues topics update … --replication-factor 3.