<div dir="ltr">Matthias,<div><br></div><div style>Thank you so much for the explanation. So if I understand it correctly, once the original master is back online as a slave, its old messages will get consumed, meaning it's possible that we will get some old, previously consumed messages again. (Since we already consumed them earlier from the new master?)</div>
<div style><br></div><div style>If this is the case, is there any way to be able to tell if this message is stale? My only guess would be through the delivery tag?</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Fri, Dec 28, 2012 at 9:22 PM, 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 29/12/12 02:17, Matthias Radestock wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 28/12/12 18:17, Eugene Vasilchenko wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Let's say I have a cluster of 3 machines running rabbit. All of my<br>
queues are durable<br>
</blockquote>
<br>
...and mirrored, presumably...<br>
</blockquote>
<br></div>
Btw, note that durability is a red herring here; queue synchronisation behaviour when nodes (re)join the cluster is the same regardless of whether the queue is durable. Durability only comes into play when the last mirror of a queue is stopped and subsequently restarted.<span class="HOEnZb"><font color="#888888"><br>
<br>
Matthias.<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><span>Front End Engineer �| �Group Commerce Inc.�</span><div><span>646-549-8891 | �<a href="mailto:evasilchenko@groupcommerce.com" target="_blank">evasilchenko@groupcommerce.com</a></span></div>
</div>