[rabbitmq-discuss] rabbitmq-discuss Digest, Vol 34, Issue 41
alexis.richardson at gmail.com
Fri Mar 26 00:15:34 GMT 2010
I agree that we should make it public as soon as we can. It's still
being worked on in relation to a customer delivery.
Can I suggest that you ping us in a month if you have not heard
anything on the usual channels by then?
On Mon, Mar 22, 2010 at 4:54 PM, David Allison <david at brightscope.com> wrote:
> I would be very interested in this guide if and when it becomes available.
> Is there a way we can be notified of it?
> Message: 1
> Date: Mon, 22 Mar 2010 12:11:42 +0000
> From: Matthew Sackman <matthew at lshift.net>
> Subject: Re: [rabbitmq-discuss] High Availability
> To: Mark Steele <msteele at beringmedia.com>
> Cc: rabbitmq-discuss at lists.rabbitmq.com
> Message-ID: <20100322121141.GC19832 at mrnibble.lshift.net>
> Content-Type: text/plain; charset=us-ascii
> On Fri, Mar 19, 2010 at 03:32:15PM -0400, Mark Steele wrote:
> If you are looking for high availability, the only way that I am aware of is
> to use something like DRBD (or SAN backed storage) along with a cluster
> resource manager (eg: corosync/heartbeat/etc) and make all your messages
> durable and persist to disk.
> You can then scale clusters (eg multiple 2-node clusters) for reaching scale
> using Erlang's native cluster capabilities without sacrificing on high
> availability. A load balancer won't help with HA unless you have some
> mechanism for ensuring messages replicate between nodes.
> Yes. We now have an OCF script and HA guide which is currently going
> through QA which makes this dance easier and documents the process.
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
More information about the rabbitmq-discuss