I've been running several quite large Percona installations(DB size
over 100Gb) for several months already on some pretty busy projects.
It runs just fine(even not sharded) except the fact once(or twice) a
month the server crashes with "Database page corruption on disk or a
failed InnoDB: file read of page XXXX". I kind of got used to this
since I have no idea why it happens(I've changed several servers,
tried different kernel versions), so I have to live with this reality.
The question is whether it's possible to make InnoDB not crash the
server upon this error but rather log this error and return a error
code to the client? The log watcher would report it to me and I'd take
some neccessary actions(e.g switch the master to the replica and
investigate the corruption).
My application is a game where several thousands can be playing
online. Corruption errors usually happen for a single player and it
would be nice to make the game temporarily unavailable for this
particular player than for all of them.
Best regards, Pavel