[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Lame duck state monitoring

From: jul
Subject: Lame duck state monitoring
Date: Sat, 17 Sep 2016 22:37:24 +0000 (UTC)

Hello monit list

I recently read Google SRE Book and there is a part on lame duck state.
Their definition: "the backend task is listening on its port and can serve, but 
is explicitely asking clients to stop sending requests"

Basically if a server is an overload state (cpu, memory, threads or whatever), 
it is put out of the queue from the load balancer for x time.
Can be the same also just after a start or a reboot for service which need time 
to be performant (some caching)

Any monit rules to do that?
for example to get out of haproxy load balancer or similar
Or doing reverse, do a check remote host from load balancer ?    



reply via email to

[Prev in Thread] Current Thread [Next in Thread]