No subject

Basically the system that consumed messages, for some
reason, was too slow. That, obviously, put a lot of stress
on RabbitMQ, and as it was before rabbit 2.0, at some point
Rabbit just died due to out-of-memory situation.

Reddit guys were unhappy to see Rabbit go down, but
in fact Rabbit was not the source of their problems.
It was just a side-effect of something else misbehaving.

Cheers,
  Marek

On Fri, Mar 11, 2011 at 19:30, Marcel Meyer <marcel.meyer at gmail.com> wrote:
> Great!=C2=A0Do you know whether this was documented as some anti-pattern?=
 Is
> there more about the specific issues they faced?
> On Fri, Mar 11, 2011 at 12:13 PM, Alexis Richardson <alexis at rabbitmq.com>
> wrote:
>>
>> Hi Marcel
>>
>> Yes, I believe so. =C2=A0 Matthew went to see them. =C2=A0As I recall th=
e main
>> issues were actually not with Rabbit, but some of how they had used
>> messaging was worth discussing.
>>
>> alexis
>>
>>
>> On Fri, Mar 11, 2011 at 5:07 PM, Marcel Meyer <marcel.meyer at gmail.com>
>> wrote:
>> > Hi there Rabbit Community,
>> > I am researching queues and found this=C2=A0thread about reddit's grip=
es
>> > (http://www.reddit.com/tb/c2spc) and noticed that RabbitMQ Support
>> > reached
>> > out to them.
>> > Were there issues resolved? They upgraded ERTS as a "stopgap" fix, but
>> > wanted to yank the technology all together. Did they?
>> > Regards,
>> > Marcel
>> > _______________________________________________
>> > rabbitmq-discuss mailing list
>> > rabbitmq-discuss at lists.rabbitmq.com
>> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>> >
>> >
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>