Fallout from WT-6602, the optimer is only started on entry to the API and as such when it's configured from the calls to wt_txn_begin, wt_txn_rollack and wt_txn_commit its not started. As such it won't timeout in the cache eviction check.
Fallout from WT-6602, the optimer is only started on entry to the API and as such when it's configured from the calls to wt_txn_begin, wt_txn_rollack and wt_txn_commit its not started. As such it won't timeout in the cache eviction check.