[rabbitmq-discuss] rabbitmq-discuss Digest, Vol 18, Issue 34

Ben Hood 0x6e6562 at gmail.com
Tue Nov 18 12:12:47 GMT 2008


On Tue, Nov 18, 2008 at 3:52 AM, Ilya Grigorik <ilya at aiderss.com> wrote:
> Interesting, this helped a bit. Got up to 2.7GB in persister, then killed
> the Erlang node once again. No kernel logs, no nothing. Grrr!

This is probably my ignorance, but I'm getting slightly confused about
what exact cause and effect you are investigating.

So forgive me if these comments are irrelevant.

If you don't use producer flow control (the channel.flow command) to
throttle message sending, eventually you will run out of resources and
you will see the behaviour that you are reporting.

Marking messages as persistent is not going to help with the current

When a message is marked as persistent, it means that there is an
additional replica of the message on disk. The purpose of the replica
is to be requeued as part of the queue recovery process, if the
message was not subsequently ack'ed by a consumer.

ATM Rabbit is not smart enough to piggy back off the journal to smooth
out memory consumption.

Also, it is questionable as to whether this would be the best way to
solve the infamous queue paging problem.

(Just trying to save you some time :-)


More information about the rabbitmq-discuss mailing list