go/badger: enable truncate to recover from corrupted value log file #2732
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.
Encountered corrupted badger value log file when running txsource tests with node restarts. Apparently badger is not at all resilient to crashes unless the truncate option is set on (which could result in data loss, but i think this should be safe as this means the crash happened while it was being written to the value log, so not yet committed).
This was also default behavior before an configuration option was added: dgraph-io/badger#452 dgraph-io/badger#740