Investigate opportunities for table drop to never return EBUSY

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines, Storage Engines - Foundations
    • 24.09
    • None
    • None

      Investigate opportunities to implement table drop so that it never returns an EBUSY error.
      If EBUSY appears internally, we could rename the underlying resources such as table URI or file and clean them up asynchronously.
      The API should either succeed or fail but it should never need to be retried.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Yury Ershov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: