2

MySQL Innodb easily get crashed, bullshit, I just restarted my server now all databases get corrupted. F*ck you OVH

Comments
  • 3
    Someone messed up good if a reboot is all it took to corrupt a mysql db.

    Those things are resilient even when you want them to die..... servers can run for years without a reboot.

    So either, you did something you shouldn't have, or they have some serious configuration issues.
  • 2
    This has zero to do with InnoDb.

    Any engine of a transactional database can only do so much...

    if you haven't configured properly the sync behaviour (e.g. disabling synchronisation on transaction end)...

    disabled / misconfigured the filesystem behaviour (e.g. write back mode ext4)…

    misconfigured sysctl (e.g. dirty writecache buffer misconfigured)...

    Wrong hardware (non enterprise, raid without bbu)...

    It's your fault.

    If anyone wonders how I came up with this stuff, it's cause I've seen it all.

    "But ShitOverflow / XY said it was for performance" is one of the most common reasons why data dies - shit copied from some dubious site without any serious consideration of consequences.

    No database can solve missing / wrong configuration - and database really need a good configuration and heavy expertise in sys -/ hardware and configuration.
  • 0
    never in my 15 years of programming and interacting with mysql innodb have i ever had it crash, let alone corrupt the db.

    problem is probably in something else, not mysql
Add Comment