Hi Matthew -- <br><br>Sorry for the delay in responding. I believe it was a long running queue and I don't recall anyone doing anything special with that queue at that time. Bizarrely, the queue did recover itself eventually although another developer told me about it and I was not there when it happened. Sorry to be short on details. If it happens again and I have more information, I will share it with you.<br>
<br>cheers,<br>SCott<br><br><div class="gmail_quote">On Sun, Apr 18, 2010 at 11:13 AM, Matthew Sackman <span dir="ltr"><<a href="mailto:matthew@lshift.net">matthew@lshift.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Sun, Apr 18, 2010 at 05:28:51PM +0100, Matthew Sackman wrote:<br>
> Yes, it recovered more off disk than it was expecting to. I have no idea<br>
> how that could happen, but quite a lot of code around there has changed<br>
> around the easter weekend, which is after the revision you're running.<br>
<br>
</div>Just some other questions: were you doing anything in particular with<br>
the queue at the time? - had you just started up Rabbit or was it a long<br>
running queue, what kind of actions were going on in the queue at the<br>
time?<br>
<font color="#888888"><br>
Matthew<br>
</font></blockquote></div><br>