Fix newly created table and drop() EBUSY issue

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • WT12.0.0, 8.2.1, 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: APIs
    • None
    • Storage Engines, Storage Engines - Foundations
    • SE Foundations - 2025-08-29
    • 3
    • v8.2, v8.1, v8.0

      This spawned out of the investigation from WT-14636. The ticket here fixes the drop EBUSY loop that occurs in MongoDB following SERVER-106947 and SERVER-106835.

      There are multiple criterias to create the drop/EBUSY loop issue.

      • The table must have logging enabled
      • The table must be empty
      • Background thread checkpoint cleanup dirties the same table

      All three criterias must be reached for the drop/EBUSY issue to occur.

            Assignee:
            Jie Chen
            Reporter:
            Jie Chen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: