there is not much overlap between the set of uses where cost prohibits having redundant
hardware and the set of uses where a system cannot be down for a reboot.
Many upgrades to Cisco equipment requires a reboot, and they are used in many places that are
extremely sensitive to outages
Posted May 1, 2008 2:33 UTC (Thu) by a9db0 (subscriber, #2181)
[Link]
Here's one: telecom
Big phone switches aren't usually redundant, and are frequently utilized 24x7x365(6). The
rise in VoIP has brought this into higher relief, and I'd expect to see some of the telecom
folks looking very hard at this.
My uptime is never that good - the power around here is way too flaky. Even for my oversized
ups.
Ksplice: kernel patches without reboots
Posted May 1, 2008 16:42 UTC (Thu) by piggy (subscriber, #18693)
[Link]
The reason big phone switches have traditionally been non-redundant is that they were
staggeringly expensive when first created.
The telecom industry is still absorbing the consequences of a 1000X improvement in both price
and performance. Reliability of individual components has also dropped by a couple orders of
magnitude, so redundancy is becoming the solution of choice.
I agree with earlier assertions that the disjunction between businesses who want long uptimes
and and those willing to put in redundant equipment is vanishingly small.
Perhaps individuals after long uptime for geek-cred are a large enough population to sustain
ksplice.