<div dir="ltr">You can also delete the vhost containing the queues - of course this deletes the exchanges in that vhost as well...<div><br></div><div>And then use the broker defs as Emile suggested but without requiring a restart.</div>
<div><br></div><div>Good luck,</div><div><br></div><div>Michael</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Oct 29, 2013 at 7:14 AM, Simon MacMullen <span dir="ltr"><<a href="mailto:simon@rabbitmq.com" target="_blank">simon@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 29/10/13 10:05, Emile Joubert wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Don't try to delete queues by modifying the contents of the data store<br>
on disk.<br>
</blockquote>
<br></div>
Yeah, seriously, this.<br>
<br>
Another option for deleting all queues (since 3.2.0) is to define a policy which gives every queue a very short expiry.<br>
<br>
$ rabbitmqctl set_policy deleter ".*" '{"expires":1}' --apply-to queues<br>
<br>
Then - assuming your queues are unused, which I assume is why you're deleting them - this will expire them near-immediately. Remember to delete the policy again afterwards, or you'll struggle to declare anything...<br>
<br>
$ rabbitmqctl clear_policy deleter<br>
<br>
Cheers, Simon<span class="HOEnZb"><font color="#888888"><br>
<br>
-- <br>
Simon MacMullen<br>
RabbitMQ, Pivotal</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com" target="_blank">rabbitmq-discuss@lists.<u></u>rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/<u></u>cgi-bin/mailman/listinfo/<u></u>rabbitmq-discuss</a><br>
</div></div></blockquote></div><br></div>