<div dir="ltr">Ron,<div><br></div><div style>You have a couple options (that I know of) if your requirements include a *single* cluster (which was not my case):</div><div style><br></div><div style>1) Increase the resources (CPU, disk, memory, network, etc.) which are available to the nodes which are hosting the master queue processes.</div>
<div style><br></div><div style>2) Ensure that the master queue processes are spread out evenly across the available nodes.</div><div style><br></div><div style>Regards,</div><div style><br></div><div style>Richard</div></div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 19, 2013 at 3:48 PM, Cordell, Ron <span dir="ltr"><<a href="mailto:Ron.Cordell@relayhealth.com" target="_blank">Ron.Cordell@relayhealth.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d">Sorry for jumping in here, but I�m a little confused on how to scale throughput in the HA scenario. If I assume that all queue are mirrored queues on a single
cluster then what are my options to adding more throughput should I need to?<u></u><u></u></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1f497d"><u></u>�<u></u></span></p>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> <a href="mailto:rabbitmq-discuss-bounces@lists.rabbitmq.com" target="_blank">rabbitmq-discuss-bounces@lists.rabbitmq.com</a> [mailto:<a href="mailto:rabbitmq-discuss-bounces@lists.rabbitmq.com" target="_blank">rabbitmq-discuss-bounces@lists.rabbitmq.com</a>]
<b>On Behalf Of </b>Richard Raseley<br>
<b>Sent:</b> Tuesday, March 19, 2013 3:36 PM<br>
<b>To:</b> Discussions about RabbitMQ<br>
<b>Subject:</b> Re: [rabbitmq-discuss] Scaling Throughput with Highly Available Queues<u></u><u></u></span></p>
<p class="MsoNormal"><u></u>�<u></u></p>
<div>
<p class="MsoNormal">Matthias,<u></u><u></u></p>
<div>
<p class="MsoNormal"><u></u>�<u></u></p>
</div>
<div>
<p class="MsoNormal">I am glad that you were able to anticipate where I was heading - that means I am not completely insane (at least as it relates to this). =]<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u>�<u></u></p>
</div>
<div>
<p class="MsoNormal">Yes, I understand that they are actually two�separate�queues (I am treating them as one logical one for purposes of discussion). In this case the lack of order preservation and visibility from one cluster to the other isn't an issue for
us. We decided not to go with two queues for the transparency reasons you mentioned.�<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u>�<u></u></p>
</div>
<div>
<p class="MsoNormal">Thanks so much for your time today.<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u>�<u></u></p>
</div>
<div>
<p class="MsoNormal">Regards,<u></u><u></u></p>
</div>
<div>
<p class="MsoNormal"><u></u>�<u></u></p>
</div>
<div>
<p class="MsoNormal">Richard<u></u><u></u></p>
</div>
</div>
</div>
</div>
<br>_______________________________________________<br>
rabbitmq-discuss mailing list<br>
<a href="mailto:rabbitmq-discuss@lists.rabbitmq.com">rabbitmq-discuss@lists.rabbitmq.com</a><br>
<a href="https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss" target="_blank">https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss</a><br>
<br></blockquote></div><br></div>