Hi Willy,
Sorry for the lack of response from the Loadbalancer.org end, I must
confess we were getting a bit confused by the descriptions :-).
The only thing in mu mind to be aware of is the design decision of the
agent to report DOWN or DRAIN on every agent request until the agent
starts responding with x% again..
Was because if you send an UP response from the agent how does the
agent know that HAProxy has read that value and acted on it? It would
need to know when it was safe to start responding with x% again?
Our primary requirement at Loadbalancer.org is for the first scenario
i.e. dynamic weight adjustment and uses standard health checks:
- inform the load balancer about the server's load to adjust the
weights, but not interact with the service's state which is
monitored using regular checks. It basically replaces the job
of the admin who would constantly re-adjust weights depending
on the servers load.
The following usage case makes sense, but isn't really a priority for us:
- offer a complete health check system to services which are not
easily checkable. In this case they would simply be used without
a regular check. This is more a service-level approach and not
a server-level one.
The third logical function for us was:
For a Windows administrator to have a simple GUI DRAIN/HALT button in
the agent, to enable quick local maintenance on the Windows backend
server without having to log into the load balancer in order to set
maintenance mode.
But again this is not really a priority with us as you say it clashes
with the CLI DRAIN logic....
On 2 December 2013 14:30, Willy Tarreau <[email protected]> wrote:
> Hi Simon,
>
> thank you for your response, I felt a little bit alone :-)
>
--
Regards,
Malcolm Turnbull.
Loadbalancer.org Ltd.
Phone: +44 (0)870 443 8779
http://www.loadbalancer.org/
