Details
-
Bug
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
None
-
Storage 2017-06-19, Storage 2017-07-10
Description
I have a CONFIG from my WT-3039 branch testing compatibility that seems to be improperly running archive during a backup. I can reliably reproduce the failure.
############################################
|
# RUN PARAMETERS
|
############################################
|
abort=0
|
alter=0
|
auto_throttle=1
|
backups=1
|
bitcnt=3
|
bloom=0
|
bloom_bit_count=34
|
bloom_hash_count=19
|
bloom_oldest=0
|
cache=37
|
checkpoints=1
|
checksum=on
|
chunk_size=5
|
compaction=0
|
compatibility=v1
|
compression=zlib
|
data_extend=0
|
data_source=file
|
delete_pct=5
|
dictionary=0
|
direct_io=0
|
encryption=none
|
evict_max=1
|
file_type=row-store
|
firstfit=0
|
huffman_key=0
|
huffman_value=0
|
in_memory=0
|
insert_pct=38
|
internal_key_truncation=1
|
internal_page_max=11
|
isolation=read-committed
|
key_gap=7
|
key_max=61
|
key_min=31
|
leaf_page_max=10
|
leak_memory=0
|
logging=1
|
logging_archive=0
|
logging_compression=zlib
|
logging_prealloc=1
|
long_running_txn=0
|
lsm_worker_threads=4
|
merge_max=10
|
mmap=1
|
ops=848740
|
prefix_compression=1
|
prefix_compression_min=2
|
quiet=1
|
read_pct=12
|
rebalance=1
|
repeat_data_pct=14
|
reverse=0
|
rows=457822
|
runs=1
|
salvage=0
|
split_pct=91
|
statistics=0
|
statistics_server=0
|
threads=3
|
timer=20
|
transaction-frequency=42
|
value_max=907
|
value_min=13
|
verify=1
|
wiredtiger_config=
|
write_pct=45
|
############################################
|
