Silent Data Corruption Is Real

Re:Silent Data Corruption Is Real by platosrepublic on Sunday March 12, 2017 @02:43PM (#13852285)

I'm not a database expert, but this seems like something I should worry about, at least a bit. Is this a problem if you store all your persistent data in a database like MySQL?

[ Parent | on HN ]

Re:Silent Data Corruption Is Real by Mister_Snuggles on Sunday March 12, 2017 @02:45PM (#13852301)

If your database does ZFS-like checksumming on all of its data, including the structures that it uses to find the data that you put in, and has the ability to correct errors, then no.

Realistically though, I don't know if MySQL has this. You'd probably be better off using a filesystem that gives these kind of guarantees and running your database on that.

[ Parent | on HN ]

Re:Silent Data Corruption Is Real by zzzcpan on Sunday March 12, 2017 @02:53PM (#13852342)

Every ACID compliant database is supposed to calculate checksums.

[ Parent | on HN ]

Re:Silent Data Corruption Is Real by copperx on Sunday March 12, 2017 @03:03PM (#13852390)

Good to know.

[ Parent | on HN ]

Re:Silent Data Corruption Is Real by blablabloe on Monday March 13, 2017 @11:02AM (#13858343)

If you run on proper enterprise gear, the likelyhood of encountering an issue like this is very, very rare.

HP/Dell/SM servers are all ECC memory top to bottom, are properly wired (snark) and SANs have also ECC everywhere. Even on the disk caches.

And in this particular instance, it was basically some private server build being messed up.

[ Parent | on HN ]