Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-6666

Start op timer when we configure it in rollback and commit

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.4.2, 4.8.0, 4.2.11, 4.0.22
    • Affects Version/s: None
    • Component/s: None
    • None
    • 2
    • Storage - Ra 2020-09-21
    • v4.4, v4.2, v4.0

      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.

            Assignee:
            luke.pearson@mongodb.com Luke Pearson
            Reporter:
            luke.pearson@mongodb.com Luke Pearson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: