3 ms·
A reboot, a software deployment (kernel upgrade), server replacement, etc. are all the same process. That simplifies things dramatically. You can micro-optimize
by jonhohle 3y ago
A reboot, a software deployment (kernel upgrade), server replacement, etc. are all the same process. That simplifies things dramatically. You can micro-optimize the 30s it takes to reboot a server, or you can simplify a runbook to have one process for any “deployment”. Different scenarios require different things but for most “web scale” things that need to be overprovisioned anyway, I’d take the simpler process.
- nickstinemates 3y agoThese servers don't take 30s to reboot. Some servers take many minutes. It's a lot.
- bradknowles 3y agoSpin new servers up before you take the old ones down. Effectively zero loss of time for that service.
- latchkey 3y agoWorse, some just don't come back without manual intervention. Power supplies don't last forever and might run fine while the machine is on, but after a reboot... boom, gone.
- yjftsjthsd-h 3y agoI'd prefer kexec to kpatch, then
- jononor 3y agoSounds like something to fix rather than to paper over?