Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-64876

Cancel any ASIO asynchronous resolution as part of a TransportLayerASIO shutdown

    • Type: Icon: Bug Bug
    • Resolution: Unresolved
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Service Arch
    • ALL
    • 11

      BF-24699 reports a leak occurring in ASIO's async_resolver internals after the server shutdown. The library offers an API to explicitly cancel any ongoing asynchronous resolution, which should get called during a shutdown to prevent any resource leak.

      A different approach would be to avoid async_resolver altogether as it relies on spawning a separate thread and calling the blocking getnameinfo.

      In general, name resolution network optimizations should be seen as an OS concern and should be left out of most user space processes.

      AC: add code which interrupts any ongoing future / async_resolution upon service termination or block termination until resolution is finished.

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            daniel.morilha@mongodb.com Daniel Morilha (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: