[rabbitmq-discuss] Ingress does not work for me and the RMQ goes down

Tim Watson tim at rabbitmq.com
Fri Apr 5 13:24:15 BST 2013


Sorry guys - just ignore me - I didn't notice that Simon had already answered (and was more on the money about the issue to boot)....

On 5 Apr 2013, at 13:23, Tim Watson wrote:

> 
> On 5 Apr 2013, at 13:07, Cermak, Marek wrote:
>> Hello everybody,
>> I continue with stress testing on limited memory. This time I have problem with RMQ going down without any warning after consuming a lot of memory.
>>  
>> Producer asks for ingress on the channel
>> amqp_channel:register_flow_handler(Channel, self()),
> 
> The process represented by 'self()' in that call should receive `#channel.flow{}` messages yes.
> 
>> The broker warns once on the console and then it is killed:
>>  
>> 13:48:24.429 [warning] Undefined: memory resource limit alarm set on node hare at xxx
>> Killed
>>  
>> shouldn't the producer be warned instead?
> 
> The producer should get throttled as well as receiving a flow notification - rabbit stops reading from the socket, at which point TCP back-pressure is exerted. Who does the killing here, i.e., where does that 'Killed' come from? Are you saying that rabbit crashes (with OOM for example) before the producer gets the flow notification?
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130405/d44fb03f/attachment.htm>


More information about the rabbitmq-discuss mailing list