News for hackers. Stuff that matters.
Re:MongoDB, Data Durability and Improvements coming in 1.8 by harryh on Monday January 10, 2011 @05:57PM (#2090055)
Because single server durability is a myth when hardware can fail at any time.
Re:MongoDB, Data Durability and Improvements coming in 1.8 by aneth on Monday January 10, 2011 @06:07PM (#2090085)
A city could be destroyed by a nuclear bomb at any time - that doesn't mean components of a system shouldn't be reasonably durable. Often it's impractical or unnecessary to have multiple servers for a proof-of-concept, a staging/test server, etc., yet it would be nice to not have to start from scratch, or to deal with backups, just because the database is so fragile. Basically, having a non-durable system forces you to take unnecessary precautions on non-critical systems because of the higher likelihood of failure and lost time investment.
Re:MongoDB, Data Durability and Improvements coming in 1.8 by lwat on Monday January 10, 2011 @06:04PM (#2090075)
We're talking about data durability. When my SQL server crashes due to hardware failure I know that when I eventually get it back up and running the data will be consistent with at worst the last couple of transactions being rolled back.
Re:MongoDB, Data Durability and Improvements coming in 1.8 by harryh on Monday January 10, 2011 @07:39PM (#2090336)
This is most certainly not true. Disks fail in ways where the whole volume becomes unreadable all the time.
Re:MongoDB, Data Durability and Improvements coming in 1.8 by lwat on Monday January 10, 2011 @07:52PM (#2090379)
What I'm saying is that I can go up to my SQL server and disconnect the power cord and my database will not be corrupt when I start it back up. Sure if your HDD gets taken out by a meteor then nothing will save you but that's why you have backups.
Re:MongoDB, Data Durability and Improvements coming in 1.8 by bsg75 on Monday January 10, 2011 @08:13PM (#2090439)
Not guaranteed. I have had more than one customer experience hardware failure, resulting in a corrupt or suspect SQL Server database, that was unrecoverable via normal means.

In each of the cases where the customer had a true standby system, implemented via replication, log shipping, or mirroring, they were able to failover with little (log shipping) or no data loss.

In the cases where they had a single, standalone server, the option was to restore the last known good backup, or sent the database files had to Microsoft for analysis and repair.

ANY system (RDBMS, NoSQL, or otherwise), should have a standby replica to prevent data loss. If you data is stored on a single machine, you are doing it wrong.

Re:MongoDB, Data Durability and Improvements coming in 1.8 by lwat on Monday January 10, 2011 @08:27PM (#2090477)
I'm not disagreeing with you, all I'm saying is that SQL Server databases are built from the ground up to resist data corruption and does exceedingly well at it. Not so with NoSQL data stores.
Re:MongoDB, Data Durability and Improvements coming in 1.8 by ericflo on Monday January 10, 2011 @09:17PM (#2090580)
Not so with MongoDB. Let's please not blame all of NoSQL for MongoDB's bad design decisions.
Re:MongoDB, Data Durability and Improvements coming in 1.8 by aphyr on Tuesday January 11, 2011 @12:42AM (#2091050)
Yeah. There are several nosql backends which offer resistance to corruption under sudden failure. Bitcask, for example, is structured for on-disk data durability using some of the ideas for log-structured filesystems.