[rabbitmq-discuss] Confirm if the message was published

[Guilherme Labigalini]

Thanks for your input!

I deleted some files and now I've 5GB of free disk space. My disk low
watermark is 953.7MB; And the same problem happens, I started the test
application that send messages with 100k in the message body and after 3k
messages sent the WaitForConfirms method is returning timeout.

Then I change my timeout from 5 seconds to 30 seconds and it worked until
my disk was full - that is great.

Looks like RabbitMQ needs more time to confirm/write messages to disk when
the queue size is big (like 2GB).

There is any recommendation about how much data I can "store" the message
queues?

Thanks!


On Thu, Jul 11, 2013 at 6:56 AM, Matthias Radestock
<matthias at rabbitmq.com>wrote:

> On 11/07/13 10:44, Emile Joubert wrote:
>
>> On 10/07/13 18:24, Guilherme Labigalini wrote:
>>
>>  when there is no free diskspace on the server, the commit operation
>>> is waiting forever.
>>>
>>
>>
>> You are probably crossing the disk free limit.
>>
>
> And that would also be the reason why the WaitForConfirms call times out.
>
> When the disk free space alarm is raised, publishing connections are
> blocked. Messages will be stuck in network buffers until the alarm
> condition is resolved, hence they won't be processed, let alone confirmed.
>
> Matthias.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rabbitmq.com/pipermail/rabbitmq-discuss/attachments/20130711/dda435dd/attachment.htm>