Hacker News Reader

Yes, I wonder that too - complete node failure is the nicest failure that can happen. (See e.g. http://danluu.com/limplock/, because Dan Luu's site is always excellent.)

"We rewrote the service for improved maintainability" seems an important part of this blog post.

View on HN

I wonder if they have a service that automatically detects all those failures and terminates the entire node instead?

I was thinking along these lines as well. Possibly they have other checks and balances in place for less than death situations for servers like high CPU usage and those situations result in another mechanism killing the server which is the same as what this solution provides.

We do: http://techblog.netflix.com/2015/07/tracking-down-villains-o...

Reply on news.ycombinator.com