-
Notifications
You must be signed in to change notification settings - Fork 872
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Block execution of database if data corruption on disk is detected #7540
Comments
I like this. And if you could provide a listener for such event, running in HA could automatically re-deploy the corrupted database to the server. |
@lvca this tool is used to indicate that HW is broken we detect not damage of records because of bugs in database but damage of records because of damage of HW. I can not have a link by hand but Redis guys added similar functionality to their database and found that quite a lot of servers have problems with HW. So our main intention is to sort out bug reports which were caused by issues in HW. Anyway, functionality will be implemented exactly using the listener so you can use it too to replace DB. But probably because HW is broken, DB will be broken soon again and there is no point to replace it. |
Fine for me. |
fixed |
We implemented a feature which allows detecting whether data are broken on disk by checking them using CRC32 code. But it this moment we by default put the warning message in a log, and that is it. It will take a while till user notices this message. Data structures may be damaged even more till warning will be noticed. There is no point to run the database with corrupted data structures. We should use the same approach which we use to switch database in read-only mode when space on a disk is exhausted to switch in in read-only mode when data corruption on disk is detected.
The text was updated successfully, but these errors were encountered: