[rabbitmq-discuss] Queue clustering
alexis.richardson at cohesiveft.com
Wed Nov 14 13:14:58 GMT 2007
We used logfiles to persist queues for speed and as a known best practice.
Using mnesia for persisting queues is a good idea for several reasons,
not least the manageability and quality of mnesia, but of course also
to provide several queue failover patterns 'out of the box'. Other
persistence models may also be attractive.
We'd planned to look at this in more detail after AMQP 0-10 is out
because that will define some of the failover and HA behaviours for
AMQP. Given that 0-10 is on its way soon, we've begun to look at this
informally, and would be delighted to move that discussion 'on list'.
What ideas would you recommend pursuing first? Our back-of-envelope
idea was, very simply, to see how a broker would perform with mnesia
instead of the current logger, using a bit of custom coding. This
might suggest good ways to go forward more systematically, and indeed
if this was even a good idea to pursue.
On Nov 14, 2007 7:53 AM, Ben Hood <0x6e6562 at gmail.com> wrote:
> Dear list,
> This is probably a stupid question, but why is mnesia not suitable for
> backing queues?
> Given that rabbit already uses mnesia to replicate exchange state, and
> that you get a reference to the first and last items of a sorted
> table, is there some obvious problem with using mnesia that I can't see?
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
+44 20 7617 7339 (UK)
+44 77 9865 2911 (cell)
+1 650 206 2517 (US)
More information about the rabbitmq-discuss