[rabbitmq-discuss] rabbit chokes?

[Owen Nelson]

Yeah, I use 2 separate vhosts, one for development and one for
production.  Good to know!

Paul Jones wrote:
> Unfortunately, its just been pointed out to me that you are using a
> non-default vhost which the BQL tool currently can't do. So perhaps it
> won't be useful in your situation at this point in time. Sorry about that.
>
> On Thu, Nov 5, 2009 at 3:47 PM, Paul Jones <pauljones23 at gmail.com
> <mailto:pauljones23 at gmail.com>> wrote:
>
>     Hi Owen,
>
>     You've got two options for this. Either you can write a client app
>     to do a queue purge, or you can install the BQL plugin which
>     provides a console that you can execute commands on.
>
>     The page at http://www.rabbitmq.com/rabbitmq-bql.html#installation
>     discusses installation of this plugin - once you've done that, you
>     should be able to execute a command such as:
>       BQL> purge queue celerygraph;
>
>     Thanks,
>     Paul.
>
>
>     On Thu, Nov 5, 2009 at 2:22 PM, Owen Nelson <onelson at ringling.edu
>     <mailto:onelson at ringling.edu>> wrote:
>
>         Perhaps this is the culprit?
>
>         rabbitmqctl list_queues -p gmate_test
>         Listing queues ...
>         celerygraph     277558
>         celery  0
>         ...done.
>
>         What's the best way to clear that out?  Looking at the man
>         page for
>         rabbitmqctl, the only thing I see that would potentially do it
>         would be
>         to reset the node, then rebuild the vhosts/users.  Is that the
>         only way?
>
>
>         Matthias Radestock wrote:
>         > Owen,
>         >
>         > Owen Nelson wrote:
>         >> =INFO REPORT==== 1-Nov-2009::09:13:43 ===
>         >>     alarm_handler: {set,{system_memory_high_watermark,[]}}
>         >>
>         >> =INFO REPORT==== 1-Nov-2009::09:13:44 ===
>         >>     alarm_handler: {clear,system_memory_high_watermark}
>         >
>         > These messages indicate that rabbit is running low on memory
>         and is
>         > attempting to throttle producers.
>         >
>         > I recommend checking the status of your rabbit using the
>         'rabbitmqctl
>         > list_* ...' commands. Chances are you have lots of messages
>         in queues,
>         > or perhaps lots of queues, exchanges or bindings.
>         >
>         >
>         > Regards,
>         >
>         > Matthias.
>
>         _______________________________________________
>         rabbitmq-discuss mailing list
>         rabbitmq-discuss at lists.rabbitmq.com
>         <mailto:rabbitmq-discuss at lists.rabbitmq.com>
>         http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>
>