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 |
|---|---|---|
| win | ||
| README | -rw-r--r-- | 405 bytes |
| atomic_pointer.h | -rw-r--r-- | 4.9 KB |
| likely.h | -rw-r--r-- | 780 bytes |
| port.h | -rw-r--r-- | 917 bytes |
| port_example.h | -rw-r--r-- | 4.5 KB |
| port_posix.cc | -rw-r--r-- | 3.0 KB |
| port_posix.h | -rw-r--r-- | 13.1 KB |
| stack_trace.cc | -rw-r--r-- | 3.3 KB |
| stack_trace.h | -rw-r--r-- | 678 bytes |
Computing file changes ...
