eff5e076f5
Summary: unordered_write is incompatible with non-zero max_successive_merges. Although we check this at runtime, we currently don't prevent the user from setting this combination in options. This has led to stress tests to fail with this combination is tried in ::SetOptions. The patch fixes that and also reverts the changes performed by https://github.com/facebook/rocksdb/pull/6254, in which max_successive_merges was mistakenly declared incompatible with unordered_write. Pull Request resolved: https://github.com/facebook/rocksdb/pull/6284 Differential Revision: D19356115 Pulled By: maysamyabandeh fbshipit-source-id: f06dadec777622bd75f267361c022735cf8cecb6 |
||
|---|---|---|
| .. | ||
| fault_injection_test_env.cc | ||
| fault_injection_test_env.h | ||
| mock_time_env.h | ||
| sync_point_impl.cc | ||
| sync_point_impl.h | ||
| sync_point.cc | ||
| sync_point.h | ||
| testharness.cc | ||
| testharness.h | ||
| testutil.cc | ||
| testutil.h | ||
| transaction_test_util.cc | ||
| transaction_test_util.h | ||