[rabbitmq-discuss] RabbitMQ 1.8.0 release

[Alexis Richardson]

On Thu, Jun 17, 2010 at 9:17 AM, techabc <techabc at gmail.com> wrote:
> AMQP 1.0 has been voted as "Recommended" status.
> Dose rabbitMQ follow it? And the Roadmap?

None of the brokers 'follow' AMQP 1.0 'Recommended Draft'.

In time, we hope all brokers will implement a GA / Final version of
AMQP 1-0.  This will take a little while.  Please be patient.

At this stage you can help by volunteering effort around the Draft
spec.  Would you like to do so?

alexis



> 2010/6/17 Ilya Grigorik <ilya at postrank.com>
>>
>> Aha, thanks for the tip Matthew.
>>
>> On Wed, Jun 16, 2010 at 12:19 PM, Matthew Sackman <matthew at rabbitmq.com>
>> wrote:
>>>
>>> On Wed, Jun 16, 2010 at 12:02:08PM -0400, Ilya Grigorik wrote:
>>> > One of our rabbit servers is ~7GB RAM, and I know that if we push over
>>> > 250K
>>> > messages into it (heavy messages), and the server hits swap, the server
>>> > starts crawling.. to the tune of being able to get only a few messages
>>> > a
>>> > second (out). Meaning, we need to nuke the entire queue to bring the
>>> > server
>>> > back to functional.
>>>
>>> You need to be using the new persister branch - compile from source, but
>>> set the server to use branch "bug21673". The raison d'être of the new
>>> persister is to solve problems such as the one you describe.
>>>
>>> Matthew
>>
>>
>> _______________________________________________
>> rabbitmq-discuss mailing list
>> rabbitmq-discuss at lists.rabbitmq.com
>> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>>
>
>
> _______________________________________________
> rabbitmq-discuss mailing list
> rabbitmq-discuss at lists.rabbitmq.com
> http://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss
>
>