ethdb/pebble: fsync for batch writes (#27522)
This is likely the culprit behind several data corruption issues, e.g. where data has been written to the freezer, but the deletion from pebble does not go through due to process crash.
This commit is contained in:
parent
6d2aeb43d5
commit
713fc8bbe6
@ -535,7 +535,7 @@ func (b *batch) Write() error {
|
||||
if b.db.closed {
|
||||
return pebble.ErrClosed
|
||||
}
|
||||
return b.b.Commit(pebble.NoSync)
|
||||
return b.b.Commit(pebble.Sync)
|
||||
}
|
||||
|
||||
// Reset resets the batch for reuse.
|
||||
|
Loading…
Reference in New Issue
Block a user