> On Mar 31, 2012, at 11:06 PM, David Birdsong wrote: >> On Sat, Mar 31, 2012 at 7:55 PM, Kevin Heatwole <[email protected]> wrote: >>> I would plan to automate this by having all servers included in the haproxy >>> config but only the first server would initially be UP and all others DOWN. >>> When a server handles a request, it makes sure that its next server is >>> activated. When a server doesn't handle any requests for some time, it >>> deactivates its next server (if any). >> >> You could implement this by monitoring your available slots on a >> backend, once the slots decrease %N of total slots, spin up new >> instances. Apply the same logic in reverse to turn off nodes. > I just noticed in the documentation that the http-check can send its state. This seams to contain enough info (scur and qcur) for a script to decide to activate or deactivate a server. I like that this decision can be made using the stats from the load balancer.
So, I think this is sufficient for my needs and I don't need a new balance algorithm.
