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

per-operation progress callback and abort

    • Type: Icon: New Feature New Feature
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None

      Feature needs to report progress on an individual operation and allow the operation to be aborted.

      A brief conversation with geert.bosch led to this:

      WT_SESSION.progress(WT_SESSION session,
          void (*callback)(WT_SESSION *session, uint64_t count, bool *stop))
      

      which declares a callback function long-running WiredTiger operations call with the session handle, a work-chunk count, and a boolean. If, on return, stop is true, the operation will be aborted, if that's possible.

      I think the set of long-running operations are: compact, rebalance, salvage, upgrade and verify.

      michael.cahill, alexander.gorrod, thoughts?

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            keith.bostic@mongodb.com Keith Bostic (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: