mirror of https://github.com/facebook/rocksdb.git
Fix txn_write_policy check in crash test script (#12683)
Summary: Pull Request resolved: https://github.com/facebook/rocksdb/pull/12683 With optimistic transactions, the stress test parameter `txn_write_policy` is not applicable and is thus not set. When the parameter is subsequently checked, Python's dictionary `get` method returns `None`, which is not equal to zero. The net result of this is that currently, `sync_fault_injection` and `manual_wal_flush_one_in` are always disabled in optimistic transaction mode (most likely unintentionally). Reviewed By: cbi42 Differential Revision: D57655339 fbshipit-source-id: 8b93a788f9b02307b6ea7b2129dc012271130334
This commit is contained in:
parent
62600cb2d4
commit
ad6f6e24c8
|
@ -798,7 +798,7 @@ def finalize_and_sanitize(src_params):
|
|||
dest_params["unordered_write"] = 0
|
||||
# For TransactionDB, correctness testing with unsync data loss is currently
|
||||
# compatible with only write committed policy
|
||||
if dest_params.get("use_txn") == 1 and dest_params.get("txn_write_policy") != 0:
|
||||
if dest_params.get("use_txn") == 1 and dest_params.get("txn_write_policy", 0) != 0:
|
||||
dest_params["sync_fault_injection"] = 0
|
||||
dest_params["manual_wal_flush_one_in"] = 0
|
||||
# Wide column stress tests require FullMergeV3
|
||||
|
|
Loading…
Reference in New Issue