[rabbitmq-discuss] Queue mirroring policy ordering

Simon MacMullen simon at rabbitmq.com
Wed Aug 21 10:09:24 BST 2013


Policies can be given an optional priority (if you don't specify it the 
default is 0, it can be any integer). Highest priority wins. If two 
policies with the same priority match, the choice is arbitrary.

Cheers, Simon

On 21/08/13 05:36, Dan_b wrote:
> Hi guys,
>
> Sorry about the spate of questions, but I've just recently started managing
> a rabbitmq environment and been tasking with upgrading and scaling from a
> single node to multiple with mirorring.
>
> For scaling we would like to move some of our queues to additional
> master/slave pairs using a nodes policy.  My question is how is the order of
> those policies interpreted?  Could we have a policy for specific queues and
> then have a catch all policy (using a .* for example) to mirror the
> remaining queues?  Should the more specific policy come first or last?
>
> Cheers
> Dan
>
>
>
> --
> View this message in context: http://rabbitmq.1065348.n5.nabble.com/Queue-mirroring-policy-ordering-tp28982.html
> Sent from the RabbitMQ mailing list archive at Nabble.com.
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>


-- 
Simon MacMullen
RabbitMQ, Pivotal


More information about the rabbitmq-discuss mailing list