rocksdb/java
Igor Canadi 35ca59364c Don't let flushes preempt compactions
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
2015-07-17 12:02:52 -07:00
..
benchmark/src/main/java/org/rocksdb/benchmark Bugfix remove deprecated option use which was removed in previous commit 019ecd1932 2015-04-30 23:16:04 +01:00
crossbuild
rocksjni Don't let flushes preempt compactions 2015-07-17 12:02:52 -07:00
samples/src/main/java Fixed a typo in RocksDBSample.java 2015-03-25 11:09:30 -07:00
src Merge pull request #639 from cleaton/setMaxTableFileSize 2015-07-14 23:23:06 +02:00
HISTORY-JAVA.md Update HISTORY.md for 3.10.0 2015-03-24 16:39:39 -07:00
jdb_bench.sh Moved Java Benchmark main classes into benchmark/src/main/java 2015-02-01 20:05:10 +00:00
Makefile Resolve Java test dependencies from local maven repo if present 2015-07-14 18:42:33 +01:00
RELEASE.md
rocksjni.pom [RocksJava] Maven build fix 2015-03-24 22:52:30 +01:00