RabbitMQ Messaging & Async Systems · Aula

Filas espelhadas para HA

Implemente filas espelhadas para replicar mensagens em vários nós do cluster. Obtenha alta disponibilidade para suas filas, garantindo que as mensagens sobrevivam a falhas nos nós.

Aula 3 de 411 etapas

Filas espelhadas para HA é uma aula grátis de RabbitMQ Messaging & Async Systems no CoddyKit. Esta é a aula 3 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de RabbitMQ Messaging & Async Systems, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de RabbitMQ Messaging & Async Systems inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Intro to Mirrored Queues

In a RabbitMQ cluster, queues are by default located on a single node. If that node fails, any messages in its queues (and the queues themselves) become unavailable until the node recovers.

Mirrored queues solve this by replicating queue contents across multiple nodes. This ensures high availability (HA) and fault tolerance for your messages.

Why Use Mirrored Queues?

Imagine a critical application where losing messages or experiencing downtime is unacceptable. Mirrored queues provide:

High Availability: If the node hosting the primary queue fails, a replica can take over seamlessly.
Data Durability: Messages are stored on multiple nodes, protecting against single-node failures.
Fault Tolerance: The system can continue operating even if some nodes go offline.

They are essential for robust, production-grade RabbitMQ deployments.

Master & Replica Architecture

When a queue is mirrored, one node hosts the master (or primary) queue. All other nodes hosting mirrors run replicas.

All operations for a mirrored queue (publishing, consuming, adding messages) are first handled by the master. The master then replicates these operations to all its replicas.

Configuring Mirroring with Policies

You don't configure mirroring directly on individual queues. Instead, you use policies. A policy is a set of rules that apply to queues whose names match a specific pattern.

This allows you to define mirroring behavior for many queues at once, or for queues created in the future, without modifying client code.

Policy Example: Mirror All Queues

Here's how to create a policy named ha-all that mirrors all queues (matching ".*") to all nodes in the cluster ("ha-mode":"all").

You'd typically run this command on one of your RabbitMQ cluster nodes via the command line.

rabbitmqctl set_policy ha-all ".*" '{"ha-mode":"all"}' --apply-to queues

Understanding ha-mode Options

The ha-mode argument in a policy defines how mirroring should behave:

all: The queue will be mirrored to all nodes in the cluster.
exactly: The queue will be mirrored to a specific number of nodes (e.g., {"ha-mode":"exactly", "ha-params":2}).
nodes: The queue will be mirrored to a specific list of named nodes (e.g., {"ha-mode":"nodes", "ha-params":["rabbit@node1", "rabbit@node2"]}).

Producers & Mirrored Queues

From a producer's perspective, interacting with a mirrored queue is no different than a non-mirrored one. The client connects to any node in the cluster, and RabbitMQ handles routing the message to the master queue for mirroring.

Try running this simple Java producer:

import com.rabbitmq.client.Channel;
import com.rabbitmq.client.Connection;
import com.rabbitmq.client.ConnectionFactory;

public class Producer {
  private final static String QUEUE_NAME = "my_mirrored_queue";

  public static void main(String[] argv) throws Exception {
    ConnectionFactory factory = new ConnectionFactory();
    factory.setHost("localhost"); // Connect to any cluster node
    try (Connection connection = factory.newConnection();
         Channel channel = connection.createChannel()) {
      // Declare a durable queue (important for mirrored queues)
      channel.queueDeclare(QUEUE_NAME, true, false, false, null);
      String message = "Hello, Mirrored Queue!";
      channel.basicPublish("", QUEUE_NAME, null, message.getBytes("UTF-8"));
      System.out.println(" [x] Sent '" + message + "'");
    }
  }
}

Consumers & Mirrored Queues

Similarly, consumers don't need special logic to consume from a mirrored queue. They simply connect to a node and subscribe to the queue.

If the master queue fails, RabbitMQ automatically promotes a replica to master, and consumers transparently switch to the new master (though a brief reconnect might be needed).

Run this consumer example:

import com.rabbitmq.client.Channel;
import com.rabbitmq.client.Connection;
import com.rabbitmq.client.ConnectionFactory;
import com.rabbitmq.client.DeliverCallback;

public class Consumer {
  private final static String QUEUE_NAME = "my_mirrored_queue";

  public static void main(String[] argv) throws Exception {
    ConnectionFactory factory = new ConnectionFactory();
    factory.setHost("localhost"); // Connect to any cluster node
    Connection connection = factory.newConnection();
    Channel channel = connection.createChannel();

    channel.queueDeclare(QUEUE_NAME, true, false, false, null);
    System.out.println(" [*] Waiting for messages. To exit press CTRL+C");

    DeliverCallback deliverCallback = (consumerTag, delivery) -> {
      String message = new String(delivery.getBody(), "UTF-8");
      System.out.println(" [x] Received '" + message + "'");
    };
    // Basic consume with auto-acknowledgement
    channel.basicConsume(QUEUE_NAME, true, deliverCallback, consumerTag -> {});
  }
}

Failover & Replica Sync

When a master node fails, RabbitMQ elects a new master from the available replicas. This new master takes over, and message processing continues without data loss.

If a node with a replica rejoins the cluster, or a new node is added, the replica will synchronize its contents with the current master. This ensures all messages are consistent across the mirrored queue instances.

Quick Check: Mirrored Queues

You've learned about the importance and mechanics of mirrored queues. Let's test your understanding.

Responda na aula interativa

Recap: Mirrored Queues for HA

We've explored mirrored queues, a crucial feature for ensuring high availability and data durability in RabbitMQ clusters.

Mirrored queues replicate messages across master and replica nodes.
They are configured using policies, allowing flexible control over mirroring behavior.
Client applications (producers/consumers) interact with mirrored queues transparently.
In case of a master node failure, a replica is promoted, ensuring continuous service and message safety.

This mechanism is vital for building robust, fault-tolerant messaging systems.

Grátis para começar

Aprenda RabbitMQ Messaging & Async Systems com um tutor de IA — grátis

Escreva e execute código real no seu navegador, obtenha ajuda instantânea de um tutor de IA 24/7 e continue de onde parou na web ou no app.

Cursos: 11
Aulas: 44

Começar a aprender grátis Ver o curso completo

Perguntas Frequentes

A aula “Filas espelhadas para HA” é grátis?

Sim — o texto completo de “Filas espelhadas para HA” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de RabbitMQ Messaging & Async Systems, atualize para CoddyKit PRO. O curso de RabbitMQ Messaging & Async Systems inclui 4 aulas no total.

O que vou aprender em “Filas espelhadas para HA”?

Implemente filas espelhadas para replicar mensagens em vários nós do cluster. Obtenha alta disponibilidade para suas filas, garantindo que as mensagens sobrevivam a falhas nos nós. Você pratica RabbitMQ Messaging & Async Systems com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar RabbitMQ Messaging & Async Systems?

Nenhuma experiência prévia é necessária. RabbitMQ Messaging & Async Systems no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 3 de 4.

Quanto tempo leva a aula “Filas espelhadas para HA”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de RabbitMQ Messaging & Async Systems?

Sim. Cada aula de RabbitMQ Messaging & Async Systems inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

← Voltar para RabbitMQ Messaging & Async Systems