-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Labels:
-
StorEng - Refinement Pipeline
Summary
So far I've only seen this in patch builds, but when running perf-test-mongodb-large-oplog in I've been hitting the following concurrent conflict:
[2022/11/17 22:47:41.151] Error: Truncate: failed Error: WT_ROLLBACK: conflict between concurrent operations [2022/11/17 22:47:41.153] truncate failed for: 000000000000000...000000000000498751, range: 684070 Error: WT_ROLLBACK: conflict between concurrent operations
This seems to fire more often when I increase the number of runs (maxruns) and reducing runtime (run_time). To do so I've made the following changes in evergreen.yml:
perf-test-name: mongodb-large-oplog.wtperf - maxruns: 1 - wtarg: -ops ['"load", "insert", "truncate", "database_size"'] + maxruns: 10 + wtarg: -ops ['"load", "insert", "truncate", "database_size"'] -args ['"-o run_time=120"']
One interesting feature of this test is the length of the keys. For example the key from the error above is 8191 characters long.