Revision 2c1ef0692b393014613bdf4af623c9dc487f613c authored by Igor Canadi on 22 April 2014, 00:45:04 UTC, committed by sdong on 22 April 2014, 01:08:49 UTC
Summary: Calling Fsync()/Sync() on a file should give the guarantee that whatever you written to the file is now persisted. This is currently not the case, since we might have some data left in application cache as we do Fsync()/Sync(). For example, BuildTable() calls Fsync() without the flush, assuming all sst data is now persisted, but it's actually not. This may result in big inconsistencies.

Test Plan: no test

Reviewers: sdong, dhruba, haobo, ljin, yhchiang

Reviewed By: sdong

CC: leveldb

Differential Revision: https://reviews.facebook.net/D18159
1 parent 25fef46
History
File Mode Size
build_tools
coverage
db
doc
hdfs
helpers
include
java
linters
port
table
tools
util
utilities
.arcconfig -rw-r--r-- 246 bytes
.clang-format -rw-r--r-- 138 bytes
.gitignore -rw-r--r-- 311 bytes
CONTRIBUTING.md -rw-r--r-- 776 bytes
HISTORY.md -rw-r--r-- 4.9 KB
INSTALL.md -rw-r--r-- 3.3 KB
LICENSE -rw-r--r-- 1.6 KB
Makefile -rw-r--r-- 19.9 KB
PATENTS -rw-r--r-- 1.4 KB
README -rw-r--r-- 2.9 KB
README.fb -rw-r--r-- 96 bytes

README

back to top