Understand why connection close may return EBUSY

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines, Storage Engines - Foundations
    • StorEng - Defined Pipeline
    • 5
    • 0

      This ticket encapsulates the work that needs to be done to understand why the connection->close() API call may return EBUSY.

        1. wt-conn-close-ebusys.png
          wt-conn-close-ebusys.png
          1021 kB
        2. wt-conn-close-ebusys.svg
          74 kB

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Etienne Petrel
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: