WT_SESSION::drop after WT_SESSION::truncate can return EBUSY indefinitely

XMLWordPrintableJSON

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

      It appears that in some cases after a WT_SESSION::truncate, a subsequent WT_SESSION::drop will return EBUSY due to the WT_UNCOMMITTED_DATA sub-level error ("the table has uncommitted data and cannot be dropped yet"). No matter how many times the WT_SESSION::drop is retried, it continues to return the same error. Note that this is occurring on a WT instance that is intentionally not taking any checkpoints.

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

              Created:
              Updated:
              Resolved: