-
Notifications
You must be signed in to change notification settings - Fork 457
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Currently we use `MemFS` in "strict" mode to test crash recovery in the following way: - at the desired crash point we call `SetIgnoreSyncs(true)` - after we close the database, we call `ResetToSyncedState()` and `SetIgnoreSyncs(false)` and proceed using the same filesystem. This model is a bit fragile in the sense that both the previous operation that we're simulating a crash of and the new operation use the same filesystem. For example, a background operation that is finishing up some cleanup could in principle interfere with the new process. We switch to a "crash clone" model, where we instead extract a crash-consistent copy of the filesystem; further testing can proceed on this independent copy. This allows for more usage patterns - e.g. we can take multiple crash clones at various points and check them all afterwards. We also add functionality to randomly retain part of the unsynced data (which is closer to what would happen in a real crash).
- Loading branch information
1 parent
de41143
commit a70d5b3
Showing
16 changed files
with
285 additions
and
244 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.