3 ms·
This could be better titled as 'Operations Magic Cure: Test Like A Madman'. It's not the act of restarting the servers that solves problems. Rather, their nig
by donw 17y ago
This could be better titled as 'Operations Magic Cure: Test Like A Madman'.
It's not the act of restarting the servers that solves problems. Rather, their nightly reboot policy forces them to have all of the infrastructure in place to be able to rotate servers in and out of service quickly. It forces them to centrally manage configuration. It forces them to architect their software and networks to handle restarts.
They use server restarts as a way to force all of these things to be in place, which isn't such a bad idea. More importantly, it doesn't sound like they use the nightly restarts as a substitute for actual troubleshooting (e.g., rebooting a server to 'fix' a problem, rather than figuring out what's really going on).
- noss 17y agoI think you are being very insightful with using this as means of forcing things to be in place. It inspired me to actually attempts something like it. Being an Erlang fan, I also recognize some other aspects of high-availability strategies such as: * http://en.wikipedia.org/wiki/Crash-only_software http://en.wikipedia.org/wiki/Crash-only_software * http://en.wikipedia.org/wiki/Microreboot http://en.wikipedia.org/wiki/Microreboot
- Confusion 17y agoHowever, you could also achieve that with one reboot a week. Rebooting every night seems overkill.