Interns with toasters: how I taught people about load balancers

Re:Interns with toasters: how I taught people about load bal... by darshitpp on Sunday April 22, 2018 @08:13AM (#16895844)

> This is what happened when one bad web server decided it was going to fail all of its requests, and would do so while incurring the absolute minimum amount of load on itself.

Good ELI5 explanation, but it doesn't really explain why the webserver failed the requests as it did. Or maybe I'm missing something?

[ Parent | on HN ]

Re:Interns with toasters: how I taught people about load bal... by masklinn on Sunday April 22, 2018 @08:45AM (#16895923)

> it doesn't really explain why the webserver failed the requests as it did. Or maybe I'm missing something?

That the article is about load-balancers and how a single "rogue actor" can have outsized effect on the entire thing. The failing webserver is besides the point.

[ Parent | on HN ]

Re:Interns with toasters: how I taught people about load bal... by darshitpp on Monday April 23, 2018 @01:26AM (#16900716)

Oh, ok

[ Parent | on HN ]

Re:Interns with toasters: how I taught people about load bal... by Twirrim on Sunday April 22, 2018 @07:38PM (#16899344)

Take your pick. There's a remarkable number of things that can cause a server to start returning 500s while the rest of the fleet is fine. Doesn't even have to be that specific server's fault (e.g. database behind it could have reached a connection limit handling the connection pools from all the other webservers, leaving this one in the dust. Fun part from this is it can result in the misbehaving server _moving_ as connections close and re-open)

[ Parent | on HN ]

Re:Interns with toasters: how I taught people about load bal... by darshitpp on Monday April 23, 2018 @01:27AM (#16900720)

Understood! Thanks for explaining!

[ Parent | on HN ]