bft blockchain consensus consistency cryptocurrency cryptography db distributed-systems go

History

Anton Kaliaev d71d1394ec call fsync after flush (Refs #573 ) short: flushing the bufio buffer is not enough to ensure data consistency. long: Saving an entry to the WAL calls writeLine to append data to the autofile group backing the WAL, then calls group.Flush() to flush that data to persistent storage. group.Flush() in turn proxies to headBuf.flush(), flushing the active bufio.BufferedWriter. However, BufferedWriter wraps a Writer, not another BufferedWriter, and the way it flushes is by calling io.Writer.Write() to clear the BufferedWriter's buffer. The io.Writer we're wrapping here is AutoFile, whose Write method calls os.File.Write(), performing an unbuffered write to the operating system, where, I assume, it sits in the OS buffers awaiting sync. This means that Wal.Save does not, in fact, ensure the saved operation is synced to disk before returning.		7 years ago
..
README.md	merge go-autofile	8 years ago
autofile.go	go-common -> tmlibs	8 years ago
autofile_test.go	go-common -> tmlibs	8 years ago
group.go	call fsync after flush (Refs #573)	7 years ago
group_test.go	go-common -> tmlibs	8 years ago
sighup_watcher.go	merge go-autofile	8 years ago

README.md

go-autofile