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

Add "cache_max_wait_us" option to WT_SESSION::commit_transaction() and WT_SESSION::rollback_transaction()

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: APIs
    • None
    • Storage Engines

      The configuration for the WT_SESSION::commit_transaction() and WT_SESSION::rollback_transaction() methods will be modified to include a new option, cache_max_wait_us. Using this flag in any other API calls will result in an error. By default, this option will be set to 0, allowing commit and rollback operations to be involved in optional cache eviction. When configured to 1, the commit and rollback operations will be explicitly prevented from participating in optional cache eviction. Once the feature flag is enabled, transaction commit and rollback operations in the server for

      • expired multi-document transactions, and
      • Committing or aborting prepared transactions (SERVER-65106)

      will be configured with cache_max_wait_us=1 as these operations cannot be blocked.

            Assignee:
            y.ershov@mongodb.com Yury Ershov
            Reporter:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: