Create macro which aborts when conn->close() returns an error code

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • WT12.0.0, 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: APIs
    • None
    • Storage Engines, Storage Engines - Foundations
    • StorEng - 2025-04-25
    • 5

      There are many functions that return an EBUSY error without logging any information. This ticket is to investigate cases where conn->close returns EBUSY without logging. A further step will be creating documentation for the server team so they can know what to do next when encountering EBUSY on conn->close. If it's challenging to target all those cases, a recommended approach could be to first add logging to functions where EBUSY is returned.

            Assignee:
            Jie Chen
            Reporter:
            Zunyi Liu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: