3 ms·

Sorry but in this case your application should have been tested to withstand all possible failure scenarios and restart scenarios so I have little sympathy. It

Sorry but in this case your application should have been tested to withstand all possible failure scenarios and restart scenarios so I have little sympathy. It genuinely sounds like you don't trust it to come back up which is not something I could sleep on. Things fail, sometimes violently. Even with our company which has in in-house ops team and our own colocated kit, we expect process failures and restarts and plan accordingly. No sleep is lost even when something explodes at 2AM (other than for the ops team, who in this case you contracted out).

mikegioia 12y ago
You're missing his point, and it's condescending/naive of you to assume that his app hasn't been tested to withstand it with no information to tell you that. My app has been thoroughly tested to withstand reboots; however, I have 22 machines with rackspace and (a) I've never tested all 22 going down at random times, and (b) I STILL want to be awake in case anything happens unexpectedly. The pain here is the timing and announcement window for those of us who want to monitor their machines for problems.
- csmitheu 12y ago
  Well when you contract out your infrastructure that really should be part of your DR plan. Analysing failure conditions is really priority one when you put your stuff on someone else's turf as you have little control over this, despite contracts etc. You did do a DR plan right and did check your contract with RackSpace? I want to be woken up if something doesn't come back, not if it does or even if it has gone into limp mode. Seriously you're looking at the wrong end of the problem.
  - mynameisvlad 12y ago
    Jesus christ dude, we get it, you're a perfect sysadmin who has clearly covered all possible bases. But others are not like you. Systems are not always 100% foolproof, people don't have comprehensive DR plans. Is it that hard for you to understand why someone may want to be up when there is a reboot? Like seriously?
kryptiskt 12y ago
> Sorry but in this case your application should have been tested to withstand all possible failure scenarios and restart scenarios so I have little sympathy. Someone who thinks they can test all possible failure scenarios is severely lacking in imagination.
- csmitheu 12y ago
  Sorry I should have used the word probable which is limited to power, network, software and storage failures. The solution to these is redundancy and to test each failure condition in succession and combinations thereof. Sure there are more possibilities, but these should all be covered with a complete fallback DR strategy i.e. if not identifiable cause X, Y or Z then assume the worse, snapshot everything for debugging later and fallback to a complete restore from scratch. The trick is to make X, Y and Z self-healing and part of your architecture provisioning. I get the feeling most people here haven't dealt with large deployments and multiple site redundancy, five-nines reliability requirements and extensive DR planning, because the above is pretty obvious to those of us who have.
  - csmitheu 12y ago
    Well it appears that 20 years' experience doesn't trump some total amateurs with a cloud to play with...
deleted 12y ago
[deleted]

mikegioia 12y ago

You're missing his point, and it's condescending/naive of you to assume that his app hasn't been tested to withstand it with no information to tell you that. My app has been thoroughly tested to withstand reboots; however, I have 22 machines with rackspace and (a) I've never tested all 22 going down at random times, and (b) I STILL want to be awake in case anything happens unexpectedly. The pain here is the timing and announcement window for those of us who want to monitor their machines for problems.

csmitheu 12y ago
Well when you contract out your infrastructure that really should be part of your DR plan. Analysing failure conditions is really priority one when you put your stuff on someone else's turf as you have little control over this, despite contracts etc. You did do a DR plan right and did check your contract with RackSpace? I want to be woken up if something doesn't come back, not if it does or even if it has gone into limp mode. Seriously you're looking at the wrong end of the problem.
- mynameisvlad 12y ago
  Jesus christ dude, we get it, you're a perfect sysadmin who has clearly covered all possible bases. But others are not like you. Systems are not always 100% foolproof, people don't have comprehensive DR plans. Is it that hard for you to understand why someone may want to be up when there is a reboot? Like seriously?

kryptiskt 12y ago

> Sorry but in this case your application should have been tested to withstand all possible failure scenarios and restart scenarios so I have little sympathy. Someone who thinks they can test all possible failure scenarios is severely lacking in imagination.

csmitheu 12y ago
Sorry I should have used the word probable which is limited to power, network, software and storage failures. The solution to these is redundancy and to test each failure condition in succession and combinations thereof. Sure there are more possibilities, but these should all be covered with a complete fallback DR strategy i.e. if not identifiable cause X, Y or Z then assume the worse, snapshot everything for debugging later and fallback to a complete restore from scratch. The trick is to make X, Y and Z self-healing and part of your architecture provisioning. I get the feeling most people here haven't dealt with large deployments and multiple site redundancy, five-nines reliability requirements and extensive DR planning, because the above is pretty obvious to those of us who have.
- csmitheu 12y ago
  Well it appears that 20 years' experience doesn't trump some total amateurs with a cloud to play with...

deleted 12y ago

[deleted]