<div dir="ltr"><div><div>We have other supporting services that require RabbitMQ and since they only accept a single host in their connection config, we need a more reliable way for them to connect. Those services work just fine with HAProxy/RabbitMQ. </div></div><div><br></div><div>The <a href="http://docs.openstack.org/high-availability-guide/content/_configure_openstack_services_to_use_rabbitmq.html">OpenStack HA guide</a> is the only document I've come across that talks about connecting to RabbitMQ by way of multiple hosts. Even the <a href="http://www.rabbitmq.com/clustering.html">RabbitMQ docs</a> mention the use of a load balancer, DNS round robin, etc.</div><div><br></div><div>So when someone reads up on RabbitMQ outside of the HA guide and sees that it works well with HAProxy for other services, I think it's understandable that they would attempt to connect OpenStack to RabbitMQ via HAProxy.</div><div><br></div><div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Mar 20, 2015 at 12:07 AM, John Dewey <span dir="ltr"><<a href="mailto:john@dewey.ws" target="_blank">john@dewey.ws</a>></span> wrote:<br><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>
Why would anyone want to run rabbit behind haproxy? I get people did it post the ‘rabbit_servers' flag. Allowing the client to detect, handle, and retry is a far better alternative than load balancer health check intervals. </div><div class=""><div class="h5">
<p style="color:rgb(160,160,168)">On Thursday, March 19, 2015 at 9:42 AM, Kris G. Lindgren wrote:</p><blockquote type="cite"><div>
<span><div><div><div>I have been working with dism and sileht on testing this patch in one of</div><div>our pre-prod environments. There are still issues with rabbitmq behind</div><div>haproxy that we are working through. However, in testing if you are using</div><div>a list of hosts you should see significantly better catching/fixing of</div><div>faults.</div><div><br></div><div>If you are using cells with the don¹t forget to also apply:</div><div><a href="https://review.openstack.org/#/c/152667/" target="_blank">https://review.openstack.org/#/c/152667/</a></div><div>____________________________________________</div><div> </div><div>Kris Lindgren</div><div>Senior Linux Systems Engineer</div><div>GoDaddy, LLC.</div><div><br></div><div><br></div><div><br></div><div>On 3/19/15, 10:22 AM, "Mark Voelker" <<a href="mailto:mvoelker@vmware.com" target="_blank">mvoelker@vmware.com</a>> wrote:</div><div><br></div><blockquote type="cite"><div><div>At the Operator¹s midcycle meetup in Philadelphia recently there was a</div><div>lot of operator interest[1] in the idea behind this patch:</div><div><br></div><div><a href="https://review.openstack.org/#/c/146047/" target="_blank">https://review.openstack.org/#/c/146047/</a></div><div><br></div><div>Operators may want to take note that it merged yesterday. Happy testing!</div><div><br></div><div><br></div><div>[1] See bottom of <a href="https://etherpad.openstack.org/p/PHL-ops-rabbit-queue" target="_blank">https://etherpad.openstack.org/p/PHL-ops-rabbit-queue</a></div><div><br></div><div>At Your Service,</div><div><br></div><div>Mark T. Voelker</div><div>OpenStack Architect</div><div><br></div><div><br></div><div>_______________________________________________</div><div>OpenStack-operators mailing list</div><div><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a></div><div><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></div></div></blockquote><div><br></div><div><br></div><div>_______________________________________________</div><div>OpenStack-operators mailing list</div><div><a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a></div><div><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a></div></div></div></span>
</div></blockquote><div>
<br>
</div>
</div></div><br>_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br></blockquote></div><br></div></div></div>