Hi,
On Wed, Feb 25, 2009 at 10:38:55PM -0800, Michael Fortson wrote:
> When trying this, I get:
> [ALERT] 056/063556 (24031) : parsing [/etc/haproxy/haproxy.cfg:290] :
> error detected while parsing ACL 'nearly_full'.
> [ALERT] 056/063556 (24031) : Error reading configuration file :
> /etc/haproxy
Right, sorry -- it's the backend connections I need to limit based on;
the frontend splits to a few backends based on various request
parameters, and only one of those will apply in this case.
I supposed I could have the current setup of:
frontend
acls
backend1
backend2
changed to something li
from my testing and from the docs it says it only applies to the frontend
that it is defined in.
-Karl
On Wed, Feb 25, 2009 at 10:57 PM, Michael Fortson wrote:
> Oops, scratch that success report... dst_conn seems to apply to all
> connections, not just the current front-end. And it doesn't take
Oops, scratch that success report... dst_conn seems to apply to all
connections, not just the current front-end. And it doesn't take an
argument. With multiple front-ends, I'm not sure how it can be used to
put a limit on only one of them.
On Wed, Feb 25, 2009 at 10:52 PM, Michael Fortson wrote
I think we're missing connslots support until the next release (3.16
is mentioned in the archives as the first that's going to have it).
Willy must be used to having it from testing the next version :)
switched to dst_conn and gt -- worked great. Thanks Karl!
On Wed, Feb 25, 2009 at 10:47 PM, K
its the -gt make it just gt.
this is what i ended up going with:
frontend priority_rails_farm xx.xx.xx.xxx:80
mode http
option forwardfor
acl priority_full dst_conn gt 4
use_backend rails_farm if priority_full
default_backend priority_rails_farm
the backend priority_rails_fa
When trying this, I get:
[ALERT] 056/063556 (24031) : parsing [/etc/haproxy/haproxy.cfg:290] :
error detected while parsing ACL 'nearly_full'.
[ALERT] 056/063556 (24031) : Error reading configuration file :
/etc/haproxy/haproxy.cfg
(haproxy version 1.3.15.7)
source:
acl nearly_full connsl
On Sun, Feb 22, 2009 at 10:03:22AM -0800, Michael Fortson wrote:
> That's really cool. I've been doing it with weighting, but this is much
> nicer.
it was proposed and developped by someone on the list (I don't remember
whom right now) for exactly this purpose.
> Am I right in assuming that in th
That's really cool. I've been doing it with weighting, but this is much
nicer.
Am I right in assuming that in this example, when nearly_full is triggered,
it will switch entirely to that? how does the balance between the two
backends happen in this instance? Should you just repeat the definition of
Hi Karl,
On Fri, Feb 20, 2009 at 02:23:37PM -0800, Karl Pietri wrote:
> Hello everyone,
> I am using haproxy with ruby on rails backend servers and am trying to
> setup a system that will have a few mongrels dedicated to priority traffic
> and spill over to the main pool if those are busy.
>
On Fri, Feb 20, 2009 at 11:23 PM, Karl Pietri wrote:
>
> Eseentially i have 2 pools. all the servers in each pool have maxconn 1
> (because mongrel sucks). a magorit of servers are in pool A and serve my
> normal traffic.
This does not answer the question of how to configure haproxy with mong
nt:* Friday, February 20, 2009 5:24 PM
> *To:* haproxy@formilux.org
> *Subject:* priority servers in an instance
>
>
>
> Hello everyone,
> I am using haproxy with ruby on rails backend servers and am trying to
> setup a system that will have a few mongrels dedicated to p
How about if you just use really large weight on the main servers, and
really low on the fall back along with balance leastconn.
From: Karl Pietri [mailto:k...@slideshare.com]
Sent: Friday, February 20, 2009 5:24 PM
To: haproxy@formilux.org
Subject: priority servers in an instance
Hello everyone,
I am using haproxy with ruby on rails backend servers and am trying to
setup a system that will have a few mongrels dedicated to priority traffic
and spill over to the main pool if those are busy.
i've attached a diagram of what i'm trying to accomplish.
Eseentially i have 2 p
14 matches
Mail list logo
