[rabbitmq-discuss] message queues in clustered mode

[Brendan Ribera]

>From the Clustering Guide (emphasis mine):

"All data/state required for the operation of a RabbitMQ broker is
replicated across all nodes, for reliability and scaling, with full ACID
properties. *An exception to this are message queues, which currently only
reside on the node that created them*, though they are visible and reachable
from all nodes. Future releases of RabbitMQ will introduce migration and
replication of message queues."

http://www.rabbitmq.com/clustering.html#clustering

-Brendan

On Thu, May 21, 2009 at 4:26 AM, <work at anomalizer.net> wrote:

> (rabbit n00b warning)
> I have two machines januty00 and jaunty01 that are running in clustered
> mode. There is a durable queue with a few messages in it. Here is the
> behaviour I am seeing:
>
>
> arvindj at jaunty00 ~ $ sudo rabbitmqctl list_queues
> Listing queues ...
> po_box  40
> ...done.
> arvindj at jaunty00 ~ $ sudo rabbitmqctl status
> Status of node rabbit at jaunty00 ...
> [{running_applications,[{rabbit,"RabbitMQ","1.5.4"},
>                        {mnesia,"MNESIA  CXC 138 12","4.4.7"},
>                        {os_mon,"CPO  CXC 138 46","2.1.8"},
>                        {sasl,"SASL  CXC 138 11","2.1.5.4"},
>                        {stdlib,"ERTS  CXC 138 10","1.15.5"},
>                        {kernel,"ERTS  CXC 138 10","2.12.5"}]},
>  {nodes,[rabbit at jaunty01,rabbit at jaunty00]},
>  {running_nodes,[rabbit at jaunty01,rabbit at jaunty00]}]
> ...done.
>
>
>
> arvindj at jaunty01 ~ $ sudo rabbitmqctl list_queues
> Listing queues ...
> po_box  40
> ...done.
> arvindj at jaunty01 ~ $ sudo rabbitmqctl status
> Status of node rabbit at jaunty01 ...
> [{running_applications,[{rabbit,"RabbitMQ","1.5.4"},
>                        {mnesia,"MNESIA  CXC 138 12","4.4.7"},
>                        {os_mon,"CPO  CXC 138 46","2.1.8"},
>                        {sasl,"SASL  CXC 138 11","2.1.5.4"},
>                        {stdlib,"ERTS  CXC 138 10","1.15.5"},
>                        {kernel,"ERTS  CXC 138 10","2.12.5"}]},
>  {nodes,[rabbit at jaunty01,rabbit at jaunty00]},
>  {running_nodes,[rabbit at jaunty00,rabbit at jaunty01]}]
> ...done.
>
>
> All looks fine when both machines are up. Now when jaunty00 goes down, the
> queue disappears from jaunty01
> arvindj at jaunty00 ~ $ sudo /etc/init.d/rabbitmq-server stop
> Stopping rabbitmq-server: rabbitmq-server.
> arvindj at jaunty01 ~ $ sudo rabbitmqctl list_queues
> Listing queues ...
> ...done.
>
>
> When I bring januty00 back, the queue reappears on jaunty01.The reverse is
> not true i.e. when jaunty01 goes down, the queue is still available on
> jaunty00
>
> My understanding was that in clustered mode, if any one of the nodes goes
> down, the queue is still available on the other nodes. What am I missing
> here?
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20090521/9740b5e3/attachment.htm