[rabbitmq-discuss] RabbitMQ Uptime

Michael Vierling

unread,

Jul 18, 2011, 9:52:38 PM7/18/11

to rabbitmq...@lists.rabbitmq.com

Since RabbitMQ is advertised to be a high availability service, I'm happy to share our uptime numbers.

RabbitMQ host Uptime:

Virginia DC

rabbit1 - 369 days

rabbit2 - 418 days

California DC

rabbit1 - 409 days

rabbit2 - 409 days

No reboots or restarts. So, according to Wikipedia we're seeing better than six nines availability. Kudos to everyone on the RabbitMQ team!

http://en.wikipedia.org/wiki/High_availability

FYI: RabbitMQ 1.7.1, Erlang R13B04 and Red Hat 5.4

Best,

Michael Vierling

Matthias Radestock

unread,

Jul 19, 2011, 3:16:28 AM7/19/11

to Michael Vierling, rabbitmq...@lists.rabbitmq.com

Michael,

On 19/07/11 02:52, Michael Vierling wrote:
> So, according to Wikipedia we're seeing better than six nines
> availability.

Congratulations!

Can you tell us a bit more about your set up? #queues, #exchanges,
#messages, msg size, etc.

> FYI: RabbitMQ 1.7.1, Erlang R13B04 and Red Hat 5.4

You really should upgrade ;)

Regards,

Matthias.
_______________________________________________
rabbitmq-discuss mailing list
rabbitmq...@lists.rabbitmq.com
https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

Eugene Kirpichov

unread,

Jul 19, 2011, 4:14:11 AM7/19/11

to Michael Vierling, rabbitmq...@lists.rabbitmq.com

Michael, did you see cases where rmq survived the failure of one node in the cluster, or a hot code upgrade, etc? That's what is most interesting :)

19.07.2011, в 5:52, Michael Vierling <MVie...@attinteractive.com> написал(а):

_______________________________________________

Matthew Sackman

unread,

Jul 20, 2011, 1:23:26 PM7/20/11

to rabbitmq...@lists.rabbitmq.com

On Tue, Jul 19, 2011 at 08:16:28AM +0100, Matthias Radestock wrote:
> >FYI: RabbitMQ 1.7.1, Erlang R13B04 and Red Hat 5.4
>
> You really should upgrade ;)

We really should implement hot code upgrades so that he can upgrade
without losing uptime! ;)

Matthew

Matthias Radestock

unread,

Jul 20, 2011, 1:26:24 PM7/20/11

to rabbitmq...@lists.rabbitmq.com

On 20/07/11 18:23, Matthew Sackman wrote:
> On Tue, Jul 19, 2011 at 08:16:28AM +0100, Matthias Radestock wrote:
>>> FYI: RabbitMQ 1.7.1, Erlang R13B04 and Red Hat 5.4
>>
>> You really should upgrade ;)
>
> We really should implement hot code upgrades so that he can upgrade
> without losing uptime! ;)

Ah, but he'd have to upgrade to the hot-code-upgrade-enabled version
first ;)

Matthias.

Gavin M. Roy

unread,

Jul 20, 2011, 1:29:36 PM7/20/11

to rabbitmq...@lists.rabbitmq.com

On Wednesday, July 20, 2011 at 1:23 PM, Matthew Sackman wrote:

On Tue, Jul 19, 2011 at 08:16:28AM +0100, Matthias Radestock wrote:
We really should implement hot code upgrades so that he can upgrade
without losing uptime! ;)

+1 :)

Reply all

Reply to author

Forward