a0cbb69421
Summary: When the secondary cache lookup fails, we may still allocate a handle and charge the cache for metadata usage. If the cache is full, this can cause the usage to go over capacity. Later, when a (unrelated) handle is released, it trips up an assertion that checks that usage is less than capacity. To prevent this assertion failure, don't charge the cache for a failed secondary cache lookup. Tests: Run crash_test Pull Request resolved: https://github.com/facebook/rocksdb/pull/8470 Reviewed By: zhichao-cao Differential Revision: D29474713 Pulled By: anand1976 fbshipit-source-id: 27191969c95470a7b070d292b458efce71395bf2 |
||
|---|---|---|
| .. | ||
| cache_bench_tool.cc | ||
| cache_bench.cc | ||
| cache_entry_roles.cc | ||
| cache_entry_roles.h | ||
| cache_entry_stats.h | ||
| cache_helpers.h | ||
| cache_test.cc | ||
| cache.cc | ||
| clock_cache.cc | ||
| clock_cache.h | ||
| lru_cache_test.cc | ||
| lru_cache.cc | ||
| lru_cache.h | ||
| sharded_cache.cc | ||
| sharded_cache.h | ||