Skip to content
DevOps AI ToolKit
Newsletter
All prompts
AI for RabbitMQ Difficulty: Advanced ClaudeChatGPTCursor

RabbitMQ Blue-Green Cluster Migration Plan Prompt

Plan a blue-green migration to a brand-new RabbitMQ cluster using Shovel to drain in-flight messages, cut clients over vhost-by-vhost, and keep a clean rollback path.

Target user
Operators replacing a RabbitMQ cluster with zero message loss
Difficulty
Advanced
Tools
Claude, ChatGPT, Cursor

The prompt

You are a senior RabbitMQ operator who has replaced live clusters using blue-green cutovers and Shovel-based message draining.

I will provide:
- Blue (current) and green (target) cluster versions, sizes, and topology
- Definitions export from blue (vhosts, exchanges, queues, bindings, policies, users)
- Client inventory (which services publish/consume to which vhosts) and reconnection capability
- Constraints (maintenance window, acceptable dual-write period, rollback requirements)

Your job:

1. **Stand up green** — import the blue definitions into green (`rabbitmqadmin`/definitions import), reconcile policies and feature flags, and verify parity before any traffic moves.

2. **Design the Shovel drain** — configure dynamic Shovels from blue queues to green to move already-enqueued messages; specify `src-uri`/`dest-uri`, `ack-mode: on-confirm`, prefetch, and which queues shovel vs. which are drained by consumers reconnecting.

3. **Sequence the cutover** — order it vhost-by-vhost or service-by-service: move consumers to green first (so nothing new is stranded on blue), then flip publishers, then shovel the remaining blue backlog; define the exact moment publishers stop writing to blue.

4. **Guarantee no loss or dup** — require idempotent consumers for the overlap window, use publisher confirms end to end, and describe how `ack-mode: on-confirm` prevents shovel message loss.

5. **Verify drain** — confirm blue queues reach zero (`list_queues messages`), green shows the expected depth and consumers, and no `unroutable`/`NotFound` errors appear.

6. **Rollback** — keep blue intact and clients able to reconnect back until green is validated; define the abort criteria and the reverse-cutover steps.

Output as: (a) green parity checklist, (b) Shovel configuration per queue, (c) ordered cutover runbook with the publisher stop-point, (d) no-loss/no-dup guarantees, (e) validation + rollback plan.

Keep blue fully operational and reversible until every queue has drained to zero on blue and green is verified.

Run this prompt with AI

Test it, get an AI-improved version, or compare models — live in the Prompt Workspace. No copy-paste.

Related prompts

More RabbitMQ prompts & error guides

Browse every RabbitMQ prompt and troubleshooting guide in one place.

Free download · 368-page PDF

Reading prompts? Get all 500 in one free PDF

500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.

  • 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
  • Instant PDF download — yours free, forever
  • Plus one practical AI-workflow email a week (no spam)

Single opt-in · unsubscribe anytime · no spam.