<div dir="ltr">On Mon, Nov 25, 2013 at 12:05 PM, Michael Klishin <span dir="ltr"><<a href="mailto:michael.s.klishin@gmail.com" target="_blank">michael.s.klishin@gmail.com</a>></span> wrote:<br><div class="gmail_extra">
<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">
<div class="im">2013/11/25 Thilo-Alexander Ginkel <span dir="ltr"><<a href="mailto:thilo@ginkel.com" target="_blank">thilo@ginkel.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
AFAIK, all messages had been properly ACKed before</blockquote></div><br></div>Does management UI or rabbitmqctl confirm this?<span class=""><font color="#888888"><br clear="all"></font></span></div></div></blockquote><div>
<br></div><div>I don't know the exact situation during the weekend, but when restoring a (one-week-old) backup [1] into a different VM (and tweaking the hostnames so that RabbitMQ starts up), I see zero unACKed messages (and that the queue actually contained > 500.000 re-surrected messages, not 250.000 as I originally stated):</div>
<div><br></div><div><div># rabbitmqctl list_queues name messages_ready messages_unacknowledged</div><div>Listing queues ...</div><div>[...]</div><div>psm_subscriber_api_production 520111 0<br></div></div><div>[...]</div>
<div><br></div><div>BTW, the same issue also happens with RabbitMQ 3.2.1 when using the backed up data (just to rule out we are hitting a bug that has been fixed a long time ago).</div><div><br></div><div>Thanks,<br>Thilo</div>
<div><br></div><div>[1] restoring a newer version is underway</div></div></div></div>