logging subsystem may block the event loop in NetworkInterfaceASIO

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Logging, Networking
    • None
    • Service Arch
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Loging calls can periodically block the calling thread in our logsystem when we fsync the log file.

      Although we have not empirically measured the impact of this on NetworkInterfaceASIO, there is an assumption in the design of NIA that threads running in the event loop should never be blocked. If the event loop is blocked by the logging subsystem, this could potentially cause network operation handling to block as well.

      We should investigate potential workarounds, including implementing limited support for asynchronous logging.

      cc schwerin acm

            Assignee:
            [DO NOT USE] Backlog - Service Architecture
            Reporter:
            Adam Midvidy (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:
              Resolved: