Open Stack

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.  

On Thursday, March 19, 2015 at 9:42 AM, Kris G. Lindgren wrote:

> I have been working with dism and sileht on testing this patch in one of
> our pre-prod environments. There are still issues with rabbitmq behind
> haproxy that we are working through. However, in testing if you are using
> a list of hosts you should see significantly better catching/fixing of
> faults.
>  
> If you are using cells with the don¹t forget to also apply:
> https://review.openstack.org/#/c/152667/
> ____________________________________________
>  
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy, LLC.
>  
>  
>  
> On 3/19/15, 10:22 AM, "Mark Voelker" <mvoelker at vmware.com (mailto:mvoelker at vmware.com)> wrote:
>  
> > At the Operator¹s midcycle meetup in Philadelphia recently there was a
> > lot of operator interest[1] in the idea behind this patch:
> >  
> > https://review.openstack.org/#/c/146047/
> >  
> > Operators may want to take note that it merged yesterday. Happy testing!
> >  
> >  
> > [1] See bottom of https://etherpad.openstack.org/p/PHL-ops-rabbit-queue
> >  
> > At Your Service,
> >  
> > Mark T. Voelker
> > OpenStack Architect
> >  
> >  
> > _______________________________________________
> > OpenStack-operators mailing list
> > OpenStack-operators at lists.openstack.org (mailto:OpenStack-operators at lists.openstack.org)
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
> >  
>  
>  
>  
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org (mailto:OpenStack-operators at lists.openstack.org)
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>  
>  
>  


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150319/fa06123a/attachment.html>