[rabbitmq-discuss] behavior when erlang processes exhausted

Aaron Westendorf aaron at agoragames.com
Thu May 26 13:25:20 BST 2011

Thanks guys, I expected that. For what it's worth, Rabbit hung in
there for several hours before finally breaching said horizon.

We're going to adjust our settings and add some monitoring for how
close we are to the limit.


On Wed, May 25, 2011 at 5:06 PM, Matthew Sackman <matthew at rabbitmq.com> wrote:
> Hi Aaron,
> On Wed, May 25, 2011 at 03:31:31PM -0400, Aaron Westendorf wrote:
>> What is the expected behavior of Rabbit when Erlang runs out of
>> processes? We had an event over the past weekend that went something
>> like this:
>>   =ERROR REPORT==== 22-May-2011::17:35:58 ===
>>   Too many processes
> Ahh well. That's a problem. Basically, we don't try to deal nicely with
> this situation, and just let the universe slowly approach its event
> horizon. So, really, the only advice I can give is to adjust the P value
> so as to have a good level of confidence that you're not going to run
> out of processes. The max value is, I think, about 4 billion, so you
> have some wiggle room.
> Matthew
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss

Aaron Westendorf
Senior Software Engineer
Agora Games
359 Broadway
Troy, NY 12180
Phone: 518.268.1000
aaron at agoragames.com

More information about the rabbitmq-discuss mailing list