4 ms·
If you can handle a server failing and you have good reporting, you can handle many of those random issues by simply rebooting the affected server. So I can see
by saulrh 10y ago
If you can handle a server failing and you have good reporting, you can handle many of those random issues by simply rebooting the affected server. So I can see them taking out things like "load up the memory" or "load up the CPU". Logic errors (bad RAM, corrupted packets, high packet loss) are another story, but I don't know if V1 did those.
- fyshotshot 10y agoSeems to me those kind of issues would be a good way to test your monitoring. For instance verifying that the appropriate people are notified or automatic action is taken when within a reasonable amount of time after the CPU on the box starts spiking.
- drdrey 10y agoWe have another system for outlier detection that can kill instances that start behaving badly in terms of CPU, response time, error rates, etc. http://techblog.netflix.com/2015/07/tracking-down-villains-outlier.html http://techblog.netflix.com/2015/07/tracking-down-villains-o...