<div dir="ltr"><div style><span style="font-family:arial,sans-serif;font-size:13px">Thanks for your input!</span></div><div style><span style="font-family:arial,sans-serif;font-size:13px"><br></span></div><span style="font-family:arial,sans-serif;font-size:13px">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.</span><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">Then I change my timeout from 5 seconds to 30 seconds and it worked until my disk was full - that is great.</div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">Looks like RabbitMQ needs more time to confirm/write messages to disk when the queue size is big (like 2GB).</div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">There is any recommendation about how much data I can "store" the message queues?</div><div style="font-family:arial,sans-serif;font-size:13px">
<br></div><div style="font-family:arial,sans-serif;font-size:13px">Thanks!</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 11, 2013 at 6:56 AM, Matthias Radestock <span dir="ltr"><<a href="mailto:matthias@rabbitmq.com" target="_blank">matthias@rabbitmq.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 11/07/13 10:44, Emile Joubert wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 10/07/13 18:24, Guilherme Labigalini wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
when there is no free diskspace on the server, the commit operation<br>
is waiting forever.<br>
</blockquote>
<br>
<br>
You are probably crossing the disk free limit.<br>
</blockquote>
<br></div>
And that would also be the reason why the WaitForConfirms call times out.<br>
<br>
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.<span class="HOEnZb"><font color="#888888"><br>
<br>
Matthias.<br>
</font></span></blockquote></div><br></div>