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

Investigate table locking during session->drop

    • Type: Icon: Technical Debt Technical Debt
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Schema Management
    • Storage Engines
    • 5
    • StorEng - Defined Pipeline

      __drop_table currently contains the following comment

          /*
           * Open the table so we can drop its column groups and indexes.
           *
           * Ideally we would keep the table locked exclusive across the drop, but for now we rely on the
           * global table lock to prevent the table being reopened while it is being dropped. One issue is
           * that the WT_WITHOUT_LOCKS macro can drop and reacquire the global table lock, avoiding
           * deadlocks while waiting for LSM operation to quiesce.
           *
           * Temporarily getting the table exclusively serves the purpose of ensuring that cursors on the
           * table that are already open must at least be closed before this call proceeds.
           */
      

      The comment first appeared here.

      We should revisit this and determine whether the global table lock is still necessary over the handle exclusive lock.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            sean.watt@mongodb.com Sean Watt
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: