News for hackers. Stuff that matters.

csmitheu

Re:Cloud Server Reboots on Saturday September 27, 2014 @01:33PM (#8377620)
Well it appears that 20 years' experience doesn't trump some total amateurs with a cloud to play with...
Re:Cloud Server Reboots on Saturday September 27, 2014 @12:50PM (#8377498)
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.

Re:Cloud Server Reboots on Saturday September 27, 2014 @12:46PM (#8377483)
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.

Re:Cloud Server Reboots on Saturday September 27, 2014 @04:58AM (#8376511)
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).

Re:PostgreSQL Outperforms MongoDB in New Round of Tests on Saturday September 27, 2014 @04:39AM (#8376481)
You are right on all counts.

As someone who evaluated and eventually recommended against implementing MongoDB for a new product, I entirely agree with you. The Mongo implementation was shot after about three months of wasted time after failure in pre-production testing. It was rolled back at great cost to SQL Server with a light document-style abstraction as Mongo failed miserably on precisely what you said: reliability, consistency, scalability and storage management.

Proper relational databases (PostgreSQL, Oracle, SQL Server in my scope of experience) can take an absolute incredible amount of punishment without breaking any guarantees. The relational bit above is optional but it is at least something you can choose to use or not.