-
Type: Bug
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
Changes for WT-6472 broke the build. There are two problems: First eviction_dirty_target and eviction_dirty_trigger will not work with inmem configurations or with the compatibility setting. Second, the eviction settings (in the normal case) sometimes trigger a different sort of error:
(py2) kodkod-aws:csuite dda$ sh timestamp_abort/smoke.sh Parent: compatibility: false, in-mem log sync: false, add timing stress: false, timestamp in use: true Parent: Create 5 threads; sleep 10 seconds CONFIG: test_timestamp_abort -h WT_TEST.timestamp-abort -T 5 -t 10 CONFIG STRING: cache_size=5M,create,debug_mode=(table_logging=true,checkpoint_retention=5),eviction_updates_target=20,eviction_updates_trigger=95,log=(archive=true,file_max=10M,enabled),session_max=2203,statistics=(fast),statistics_log=(wait=1,json=true),transaction_sync=(enabled,method=none),eviction_dirty_target=20,eviction_dirty_trigger=95 Create checkpoint thread Create timestamp thread Create 5 writer threads Thread 1 starts at 1000000000 Thread 2 starts at 2000000000 Thread 0 starts at 0 Thread 3 starts at 3000000000 Thread 4 starts at 4000000000 Checkpoint 0 complete at stable 437778. Checkpoint 1 complete at stable 607890. oldest pinned transaction ID rolled back for eviction test_timestamp_abort: FAILED: thread_run/370: cur_oplog->insert(cur_oplog): WT_ROLLBACK: conflict between concurrent operations test_timestamp_abort: process aborting test_timestamp_abort: FAILED: Child process 30284 abnormally exited: Invalid argument test_timestamp_abort: process aborting Aborted (core dumped)
We'll need some simple rollback handling to fix this.
- duplicates
-
WT-6472 Update timestamp_abort test cache configuration
- Closed