Dropping an LSM table can fail with EBUSY when no user ops are active

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • WT2.8.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • None
    • None

      While investigating a test failure, keith.bostic discovered that an LSM drop can return EBUSY, even if there are no user-operations happening on the LSM tree.

      The EBUSY return happens if a work unit is being processed while a drop is attempting to get exclusive access to the LSM tree.

            Assignee:
            Alexander Gorrod
            Reporter:
            Alexander Gorrod
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: