Revision 8cb7ad83c39379bba1dc24aca71e44f40905550f authored by Igor Canadi on 02 June 2014, 22:33:54 UTC, committed by Igor Canadi on 02 June 2014, 22:33:54 UTC
Summary: We've seen some production issues where column family is detected as stale, although there is only one column family in the system. This is a quick fix that: 1) doesn't flush stale column families if there's only one of them 2) Use 4 as a coefficient instead of 2 for determening when a column family is stale. This will make flushing less aggressive, while still keep a nice dynamic flushing of very stale CFs. Test Plan: make check Reviewers: dhruba, haobo, ljin, sdong Reviewed By: sdong Subscribers: leveldb Differential Revision: https://reviews.facebook.net/D18861
1 parent 593bb2c
| File | Mode | Size |
|---|---|---|
| auto_sanity_test.sh | -rwxr-xr-x | 2.1 KB |
| blob_store_bench.cc | -rw-r--r-- | 7.5 KB |
| db_crashtest.py | -rw-r--r-- | 4.8 KB |
| db_crashtest2.py | -rw-r--r-- | 6.1 KB |
| db_repl_stress.cc | -rw-r--r-- | 4.2 KB |
| db_sanity_test.cc | -rw-r--r-- | 5.6 KB |
| db_stress.cc | -rw-r--r-- | 60.2 KB |
| ldb.cc | -rw-r--r-- | 424 bytes |
| ldb_test.py | -rw-r--r-- | 17.0 KB |
| reduce_levels_test.cc | -rw-r--r-- | 4.9 KB |
| sst_dump.cc | -rw-r--r-- | 11.0 KB |
Computing file changes ...
