[rabbitmq-discuss] OOM kill
dmitry.andrianov at alertme.com
Sat Mar 8 12:18:22 GMT 2014
Oh, it is the bit I keep forgetting about - the fact you want to continue accepting connections to let consumers in.
But that means that is possible to DOS any internet facing Rabbit...
Are there any mechanisms in RabbitMQ to listen on two ports or network addresses at the same time while being able to set independent connection limits on these?
It would allow to limit number of clients coming from Internet while still be able to accept consumers from trusted servers.
> On 7 Mar 2014, at 17:49, Simon MacMullen <simon at rabbitmq.com> wrote:
>> On 07/03/2014 5:43PM, Jason McIntosh wrote:
>> As I recall, the memory limit doesn't prevent rabbit from using more
>> memory, it's the point at which it stops accepting new connections. It
>> would still allow existing connections to flood the system:
> It's the other way round.
> "Block connections" means "prevent existing and new connections from publishing", *not* "refuse to accept new connections".
> Because, as noted in my other mail, you could be establishing a connection to consume messages - and we don't want to discourage that!
> But as Dmitry is finding out, memory use can still increase for other reasons.
> Cheers, Simon
> Simon MacMullen
> RabbitMQ, Pivotal
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
This email is for the use of the intended recipient(s) only.
If you have received this email in error, please notify the sender immediately and then delete it.
If you are not the intended recipient, you must not use, disclose or distribute this email without the
author's prior permission. AlertMe.com Ltd. is not responsible for any personal views expressed
in this message or any attachments that are those of the individual sender.
AlertMe.com Ltd, 30 Station Road, Cambridge, CB1 2RE, UK.
Registered in England, Company number 578 2908, VAT registration number GB 895 9914 42.
More information about the rabbitmq-discuss