WT_SESSION::drop can incorrectly return EBUSY due to WT_UNCOMMITTED_DATA

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines, Storage Engines - Transactions
    • None
    • None

      It appears that in some cases WT_SESSION::drop can return EBUSY due to the WT_UNCOMMITTED_DATA sub-level error ("the table has uncommitted data and cannot be dropped yet") despite there being no uncommitted data on the table from the application's perspective. In some cases simply retrying the WT_SESSION::drop allows it to succeed, but in other cases retrying the WT_SESSION::drop continues to return EBUSY indefinitely.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: