[rabbitmq-discuss] Resource alarms in 3.1 seems to block operations other than basic.publish
watson.timothy at gmail.com
Mon May 13 20:26:02 BST 2013
On 13 May 2013, at 19:13, Michael Klishin <michael.s.klishin at gmail.com> wrote:
> 2013/5/13 Tim Watson <watson.timothy at gmail.com>
> 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?
> 4 GB. It's not a powerful machine, although it does have an SSD which should offset the effect of paging somewhat.
Yeah, but I'm kinda with Matthias on this one. If the whole machine is grinding, it sounds a lot like you've exhausted the available resources and under those circumstances a whole bunch of things are going to crawl.
>> 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?
> As far as I can tell, yes.
That's the key thing here. If the alarm isn't unset, the producer won't be able to proceed. It sounds a lot like (a) the whole os is jammed due to resource exhaustion and (b) the alarm could still be set.
If that weren't the case, I'd expect to be able to reproduce it with a much lower threshold and even if I'm wrong, it doesn't doesn't replicate for me (in terms of the queue being non-empty) even on a single host.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss