Data recovery: repair node #142
Merged
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If a database suffers from data corruption, it is important to investigate why this happens: this is usually because of unsafe simultanious multi-process access. See #48 How to protect your database from corruption
However - in the unfortunate event of data corruption, this new feature provides a way to manually repair a broken node.
When using AceBase's own binary storage engine, it is now possible to run
await db.recovery.repairNode("path/to/broken/node"). Doing so will remove or replace the reference to it from the parent node. It does not overwrite the target record to prevent possibly breaking other data.This provides a fix for TypeError: Unknown chunk type 91 while reading record at (...)
Examples:
Recommended: backup your data before performing repairs