Shovel and Federation for multi-DC in RabbitMQ - Mini Project: Build & Apply

Shovel and Federation for multi-DC

📖 Scenario: You manage two data centers (DCs) that each run RabbitMQ servers. You want to move messages between these DCs reliably. This helps keep your systems in sync and share data across locations.

🎯 Goal: Set up RabbitMQ Shovel and Federation to transfer messages from one data center to another automatically.

📋 What You'll Learn

Create a source queue named source_queue on the first RabbitMQ server.

Configure a Shovel to move messages from source_queue to a destination queue dest_queue on the second RabbitMQ server.

Set up Federation upstream to link the two RabbitMQ servers.

Verify messages are transferred correctly by printing the message count on dest_queue.

💡 Why This Matters

🌍 Real World

Many companies run multiple data centers for reliability and speed. RabbitMQ Shovel and Federation help keep messages flowing between these centers automatically.

💼 Career

Understanding Shovel and Federation is important for DevOps engineers managing distributed messaging systems and ensuring data consistency across locations.

1

Create the source queue

Create a queue named source_queue on the first RabbitMQ server using the rabbitmqadmin command.

RabbitMQ

# Use rabbitmqadmin to declare the queue source_queue
# Your code here

Hint

Use rabbitmqadmin declare queue name=source_queue durable=true to create the queue.

2

Configure the Shovel

Create a Shovel configuration named my_shovel that moves messages from source_queue on the first server to dest_queue on the second server. Use the AMQP URI amqp://user:password@second-server for the destination.

RabbitMQ

# Add shovel configuration named my_shovel with source source_queue and destination dest_queue
# Your code here

Hint

Use rabbitmqctl set_parameter shovel my_shovel '{"src-uri":"amqp://","src-queue":"source_queue","dest-uri":"amqp://user:password@second-server","dest-queue":"dest_queue"}'.

3

Set up Federation upstream

Configure a Federation upstream named upstream_dc2 on the first RabbitMQ server to connect to the second server at amqp://user:password@second-server.

RabbitMQ

# Add federation upstream named upstream_dc2 pointing to amqp://user:password@second-server
# Your code here

Hint

Use rabbitmqctl set_parameter federation-upstream upstream_dc2 '{"uri":"amqp://user:password@second-server"}'.

4

Verify message transfer

Print the message count on the dest_queue on the second RabbitMQ server using rabbitmqadmin.

RabbitMQ

# Use rabbitmqadmin to get message count on dest_queue
# Your code here

Hint

Use rabbitmqadmin -H second-server -f value list queues name=dest_queue messages to see the message count.

Practice

1. What is the main purpose of RabbitMQ Shovel in a multi-data center (multi-DC) setup?

easy

A. To encrypt messages within a single RabbitMQ server

B. To share user credentials across multiple RabbitMQ servers

C. To automatically scale RabbitMQ nodes in a cluster

D. To copy messages between queues on different RabbitMQ servers

Solution

1. Step 1: Understand Shovel's role

   Shovel is designed to move or copy messages from one queue to another, even across different RabbitMQ servers.

2. Step 2: Compare options

   Options B, C, and D describe unrelated features like credential sharing, scaling, or encryption, which are not Shovel's purpose.

3. Final Answer:

   To copy messages between queues on different RabbitMQ servers -> Option D

4. Quick Check:

   Shovel copies messages = A [OK]

Hint: Shovel moves messages between queues on different servers [OK]

Common Mistakes:

• Confusing Shovel with Federation
• Thinking Shovel manages user credentials
• Assuming Shovel handles encryption

2. Which of the following is the correct minimal configuration snippet to define a Shovel in RabbitMQ's configuration file?

easy

A. listeners:
amqp:
port: 5672

B. shovels:
my_shovel:
source-uri: amqp://
source-queue: source_queue
destination-uri: amqp://remote
destination-queue: dest_queue

C. clusters:
nodes: [rabbit@node1, rabbit@node2]

D. federation:
upstreams:
my_upstream:
uri: amqp://remote
exchanges: ["my_exchange"]

Solution

1. Step 1: Identify Shovel configuration format

   Shovel config uses 'shovels' key with shovel name and source/destination URIs and queues.

2. Step 2: Match options to Shovel syntax

   shovels: my_shovel: source-uri: amqp:// source-queue: source_queue destination-uri: amqp://remote destination-queue: dest_queue matches the correct syntax for defining a shovel. Options A, B, and C relate to listeners, federation, and clustering, not shovel.

3. Final Answer:

   shovels: my_shovel: source-uri: amqp:// source-queue: source_queue destination-uri: amqp://remote destination-queue: dest_queue -> Option B

4. Quick Check:

   Shovel config starts with 'shovels:' = D [OK]

Hint: Shovel config uses 'shovels:' with source and destination URIs [OK]

Common Mistakes:

• Confusing federation config with shovel config
• Using cluster or listener config for shovel
• Missing source or destination queue keys

3. Given a federation upstream configured to share an exchange named logs from a remote RabbitMQ server, what will happen if a message is published to the local logs exchange?

medium

A. The message will stay local and not be sent to the remote server

B. The message will be forwarded to the remote exchange automatically

C. The message will be received from the remote exchange and appear locally

D. The message will be duplicated on both local and remote exchanges

Solution

1. Step 1: Understand Federation direction

   Federation pulls messages from remote to local, not the other way around.

2. Step 2: Analyze message flow

   Publishing locally to the exchange does not send messages upstream; messages flow from remote to local only.

3. Final Answer:

   The message will stay local and not be sent to the remote server -> Option A

4. Quick Check:

   Federation pulls from remote; local publish stays local = B [OK]

Hint: Federation pulls messages from remote to local, not vice versa [OK]

Common Mistakes:

• Thinking federation pushes messages upstream
• Assuming messages duplicate automatically
• Confusing federation with shovel direction

4. You configured a Shovel to move messages from a local queue to a remote queue, but no messages appear on the remote side. Which is the most likely cause?

medium

A. The Shovel's destination URI is incorrect or unreachable

B. The local queue is empty, so no messages to move

C. The Federation plugin is not enabled on the local server

D. The RabbitMQ server is running in standalone mode

Solution

1. Step 1: Check Shovel connectivity

   If the destination URI is wrong or unreachable, messages cannot be delivered remotely.

2. Step 2: Eliminate other causes

   Local queue being empty means no messages to move, but question implies messages exist. Federation plugin is unrelated to Shovel. Standalone mode does not prevent Shovel operation.

3. Final Answer:

   The Shovel's destination URI is incorrect or unreachable -> Option A

4. Quick Check:

   Shovel needs correct destination URI = A [OK]

Hint: Check destination URI if shovel moves no messages [OK]

Common Mistakes:

• Confusing Federation plugin with Shovel
• Ignoring network or URI errors
• Assuming local queue always has messages

5. In a multi-DC RabbitMQ setup, you want to ensure messages published in any data center are available in all others with minimal delay and no duplicates. Which combination is best?

hard

A. Use only Shovel to copy messages between queues in data centers

B. Use only Federation to share queues between data centers

C. Use Federation to share exchanges and Shovel to copy queues between data centers

D. Use clustering across data centers with mirrored queues

Solution

1. Step 1: Understand Federation and Shovel roles

   Federation shares exchanges or queues, enabling message sharing with minimal delay. Shovel copies messages between queues reliably.

2. Step 2: Combine for best multi-DC setup

   Using Federation for exchange sharing ensures messages are available across DCs. Shovel ensures queues are synchronized, preventing duplicates and delays.

3. Final Answer:

   Use Federation to share exchanges and Shovel to copy queues between data centers -> Option C

4. Quick Check:

   Federation + Shovel = best multi-DC sync [OK]

Hint: Combine Federation for sharing and Shovel for copying queues [OK]

Common Mistakes:

• Relying on clustering across data centers (not recommended)
• Using only one method causing delays or duplicates
• Confusing queue sharing with exchange sharing