[rabbitmq-discuss] Resource alarms in 3.1 seems to block operations other than basic.publish
watson.timothy at gmail.com
Mon May 13 19:07:49 BST 2013
On 13 May 2013, at 18:53, Michael Klishin <michael.s.klishin at gmail.com> wrote:
> 2013/5/13 Tim Watson <tim at rabbitmq.com>
> So what am I doing wrong here?
> I don't set the watermark really low. Instead, I publish a lot of 2-16 MB messages until the regular 40%
> watermark is hit (so, a few hundreds megs total).
> Then Rabbit basically stops deliveries and as I restart apps, connections take a really long time (up to 2 minutes).
> That said, the entire OS responsiveness is terrible.
Hmm. How long did that take? I can kick off a run overnight an let it stew I suppose. How much memory has your machine got?
> Purging the queue helps with new connections but messages are still not delivered to the consumer when I restart
> the producer.
I didn't pick that up from the original post. Is this happening after the alarm has been unset?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss