DEV Community

Rasmus Larsson
Rasmus Larsson

Posted on

3

RabbitMQ Upgrade Best Practices

Some simple best practices around performing RabbitMQ upgrades.

Testing a New Version

  • Test the upgrade process.
  • Test the new version with your services/clients.
  • If doing rolling upgrades, test your services with a mixed cluster using the versions you will upgrade from/to.
  • Test rolling back.

Rolling Upgrade

Adjust according to your setup.

Per node checklist:

  • [ ] Assume roughly 5mins per node.
  • [ ] Ensure the node is not just visible in the dashboard, but also accessible via e.g. DNS names and similar.
  • [ ] Allow the cluster to stabilise with regards to replication, queue levels and similar.
  • [ ] Ensure the underlying (cloud) platform reports a steady state.
  • [ ] Ensure that clients can connect to the node and communicate.

⚠️ Rollback always takes longer than upgrade.

Release Windows

  • One release per window. If you need to do several upgrades, schedule several windows.

Image of Timescale

🚀 pgai Vectorizer: SQLAlchemy and LiteLLM Make Vector Search Simple

We built pgai Vectorizer to simplify embedding management for AI applications—without needing a separate database or complex infrastructure. Since launch, developers have created over 3,000 vectorizers on Timescale Cloud, with many more self-hosted.

Read more →

Top comments (0)

Billboard image

The Next Generation Developer Platform

Coherence is the first Platform-as-a-Service you can control. Unlike "black-box" platforms that are opinionated about the infra you can deploy, Coherence is powered by CNC, the open-source IaC framework, which offers limitless customization.

Learn more