On Wed, Sep 17, 2014 at 10:53 AM, Bill Bogstad <bogs...@pobox.com> wrote: > a trend > away from debugging problems and towards just doing reinstalls/restarts. I > think the rise of virtualization (particularly in the cloud) has > driven this. As the > tools make it easier and easier to spin up a new VM, why bother to figure out > what caused the old one to fail, just reinitalize a new one and keep going.
With virtualization (and multi-instance scale-out), it's not a disjunction: you can do BOTH (as someone pointed out up-thread). If you autostart a replacement instance (or just shift load to a N/N+m survivor) and keep the failed offline, you can debug at leisure while continuing/restoring service. [ how much debugging you can do off-line with it cut off from other tiers is a separate question, but you can at least collect 'forensics' that will be destroyed at re-start. ] -- Bill Ricker bill.n1...@gmail.com https://www.linkedin.com/in/n1vux _______________________________________________ Discuss mailing list Discuss@blu.org http://lists.blu.org/mailman/listinfo/discuss