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

Add and log connection ID in connection pool

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Service Arch
    • Service Arch Prioritized List

      The `ConnectionPool` interface has a notion of a `PoolId`, which is used to maintain separate pools for each `HostAndPort`. However, it does not seem to have a similar concept to distinguish between individual connections in each pool. As a result, many of the connection pool's logs (e.g., this one) address specific lifetime changes for individual connections (spawn, refresh, destruct) without providing a way to identify which connection this is happening to.

      Incorporating a connection ID for each connection within a `SpecificPool` would help trace through individual connection lifetimes through logs so that it's easier to correlate operation success/failure with the connection that they used.

            Assignee:
            backlog-server-servicearch [DO NOT USE] Backlog - Service Architecture
            Reporter:
            varun.ravichandran@mongodb.com Varun Ravichandran
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: