Revision dae3b5545c556e2479972a21d1ed8850aac0bae8 authored by anand76 on 28 March 2019, 22:13:02 UTC, committed by Facebook Github Bot on 28 March 2019, 22:17:13 UTC
Summary:
WAL files are currently not subject to deletion rate limiting by DeleteScheduler. If the size of the WAL files is significant, this can cause a high delete rate on SSDs that may affect other operations. To fix it, force WAL file deletions to go through the SstFileManager. Original PR for this is #2768
Pull Request resolved: https://github.com/facebook/rocksdb/pull/5116

Differential Revision: D14669437

Pulled By: anand1976

fbshipit-source-id: c5f62d0640cebaa1574de841a1d01e4ce2faadf0
1 parent a98317f
History
File Mode Size
win
README -rw-r--r-- 405 bytes
dirent.h -rw-r--r-- 1.0 KB
jemalloc_helper.h -rw-r--r-- 2.5 KB
likely.h -rw-r--r-- 690 bytes
port.h -rw-r--r-- 834 bytes
port_example.h -rw-r--r-- 3.5 KB
port_posix.cc -rw-r--r-- 6.0 KB
port_posix.h -rw-r--r-- 5.4 KB
stack_trace.cc -rw-r--r-- 3.5 KB
stack_trace.h -rw-r--r-- 648 bytes
sys_time.h -rw-r--r-- 1.1 KB
util_logger.h -rw-r--r-- 819 bytes
xpress.h -rw-r--r-- 687 bytes

README

back to top