Comment by kelnos
I feel like this obsession with zero downtime has gotten a bit silly. Sure, for some things it's damn near required (though I imagine that's fewer things than most people think), but it 100% does not matter even a little bit if HN is unavailable for 10 seconds or so.
Everyone went right for “downtime” - no, that’s not an issue. I would have expected a configuration change, which wouldn’t require a restart but might indeed result in downtime.
Or even a configuration change that some control system notices and does restart the service.
It’s the manual, hands-on connotation (maybe only in my mind) of telling someone a restart is involved. Automate this stuff - don’t want the code in the server all year? Fine, have a process rebuild and relaunch on a schedule that makes sense. Might have downtime, but definitely have less hands-on.