[rabbitmq-discuss] rabbitmq with one producer no consumer

Ovidiu Deac ovidiudeac at gmail.com
Thu Jul 15 15:18:00 BST 2010

stopping the producer is not an option because the messages come from
the outside and we don't want to lose any of them. In that case the
producer should store them locally somehow and then we get back to
storing the messages in the db.

I'm thinking that there has to be some ways to increase the number of
messages that we are able to store in the queues if the consumers die
(a worst case scenario).

On Thu, Jul 15, 2010 at 4:19 PM, Robert Raschke <rtrlists at googlemail.com> wrote:
> On Thu, Jul 15, 2010 at 12:58 PM, Ovidiu Deac <ovidiudeac at gmail.com> wrote:
>> ...and the erlang version is "R13B01"
>> On Thu, Jul 15, 2010 at 2:53 PM, Ovidiu Deac <ovidiudeac at gmail.com> wrote:
>> > I forgot to say that we are using rabbitmq 1.8.0 on linux.
>> >
>> > On Thu, Jul 15, 2010 at 2:40 PM, Ovidiu Deac <ovidiudeac at gmail.com>
>> > wrote:
>> >> We are testing a rabbitmq intalation to see how it behaves if there is
>> >> no consumer while the producer publishes messages. The point of the
>> >> test is to see what we can rely on if somehow our consumer processes
>> >> die.
>> >>
>> >> In order to do this we send persistent messages with a 300bytes
>> >> content in a loop and after 200k messages rabbitmq uses 100% processor
>> >> and is unreachable. The memory usage on the machine is only 27%. Even
>> >> when restarting the broker it won't start anymore.
>> >>
>> >> Any ideas how I can tune rabbitmq to deal with this situation?
>> >>
>> >> Thanks,
>> >> Ovidiu
>> >>
>> >
> I think you should use some flow control. If your Rabbit has the memory
> alerts turned on, then your producer can pick up the
> channel.flow/active=false and stop sending until you get the active=true.
> Otherwise your sending of persistent message will eventually make Rabbit run
> out of resources.
> Robby

More information about the rabbitmq-discuss mailing list