2 ms·
> That is, it doesn't attempt to do any work, and instead just throws back a HTTP 5xx error I'm surprised the OP doesn't suggest having your load balancer pay
by jrochkind1 12y ago
> That is, it doesn't attempt to do any work, and instead just throws back a HTTP 5xx error
I'm surprised the OP doesn't suggest having your load balancer pay attention to returned error codes.
If the load balancer knows what average amount of 500 or non-200 responses is, and one unit is returning way more than an average rate of non-succesful responses, it would make sense for the load balancer to back off sending to that machine. But maybe still send an occasional request there, so it can notice when/if it's error rate returns to normal.
Do any load balancers work like this?
- sytringy05 12y agoNot all load balancers support this (I recall some very expensive alteons that didnt) but worse is when the LB does support it but it isn't configured to check. Out of the box most LB's will do a TCP bind and if that works, then fire away. The reverse of this issue can also cause problems where you get a bad node that accepts the request but never returns (or takes 2-3 mins to respond). As a rule the timeouts will cause queuing, thread pool starvation and general not working all the way back up your request chain to whatever is facing the internet where your site will either hang or give back a 503 page.