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

Start op timer when we configure it in rollback and commit

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • WT10.0.0, 4.4.2, 4.8.0, 4.2.11, 4.0.22
    • None
    • None
    • 2
    • Storage - Ra 2020-09-21
    • v4.4, v4.2, v4.0

    Description

      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.

      Attachments

        Issue Links

          depends on

          Task - A task that needs to be done. WT-6602 Allow operation timeout ms to be passed to commit and rollback

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. WT-6507 Exit cache eviction worker after our operation has timed out

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: