<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2013/7/28 Kalin Chih <span dir="ltr"><<a href="mailto:kalinchih@gmail.com" target="_blank">kalinchih@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Question 1: Is any possible to automatically re-create the queue "rabbit_test" on the other disc node (rabbit@rabbitmq2) when the rabbit@rabbitmq1 is crash?</div></blockquote><div><br></div><div>Queue metadata (e.g. name, durability, other properties) will be available on other nodes automatically.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><br></div><div>Question 2: What is the best practice for cluster without "Mirrored Queue Behaviour"?</div>
</blockquote></div><br>It depends on what your goals and needs are. What problem are you trying to solve with clustering?</div><div class="gmail_extra">Why mirroring queue contents is not a good idea in your case?<br>-- <br>
MK<br><br><a href="http://github.com/michaelklishin" target="_blank">http://github.com/michaelklishin</a><br><a href="http://twitter.com/michaelklishin" target="_blank">http://twitter.com/michaelklishin</a><br>
</div></div>