mirror of
https://github.com/facebook/rocksdb.git
synced 2024-11-26 16:30:56 +00:00
35ca59364c
Summary: When we first started, max_background_flushes was 0 by default and compaction thread was executing flushes (since there was no flush thread). Then, we switched the default max_background_flushes to 1. However, we still support the case where there is no flush thread and flushes are done in compaction. This is making our code a bit more complicated. By not supporting this use-case we can make our code simpler. We have a special case that when you set max_background_flushes to 0, we schedule the flush to execute on the compaction thread. Test Plan: make check (there might be some unit tests that depend on this behavior) Reviewers: IslamAbdelRahman, yhchiang, sdong Reviewed By: sdong Subscribers: dhruba, leveldb Differential Revision: https://reviews.facebook.net/D41931 |
||
|---|---|---|
| .. | ||
| backupablejni.cc | ||
| checkpoint.cc | ||
| columnfamilyhandle.cc | ||
| comparator.cc | ||
| comparatorjnicallback.cc | ||
| comparatorjnicallback.h | ||
| env.cc | ||
| filter.cc | ||
| iterator.cc | ||
| loggerjnicallback.cc | ||
| loggerjnicallback.h | ||
| memtablejni.cc | ||
| merge_operator.cc | ||
| options.cc | ||
| portal.h | ||
| ratelimiterjni.cc | ||
| restorejni.cc | ||
| rocksjni.cc | ||
| slice.cc | ||
| snapshot.cc | ||
| statistics.cc | ||
| table.cc | ||
| transaction_log.cc | ||
| ttl.cc | ||
| write_batch.cc | ||
| write_batch_test.cc | ||
| write_batch_with_index.cc | ||
| writebatchhandlerjnicallback.cc | ||
| writebatchhandlerjnicallback.h | ||