connection pools in mongos and mongod don't check idle connections until used

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: Major - P3
    • 2.5.5
    • Affects Version/s: None
    • Component/s: Networking, Sharding
    • None
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This leads to the case where a server goes down and comes back up, and hours later a socket exception occurs b/c the connection was never used previously.

      EDIT:
      This is addressed by SERVER-9041 (proactively checking idle connections in the pool) and SERVER-11681 (no longer holding thread-local connections in mongos between requests)

            Assignee:
            Unassigned
            Reporter:
            Greg Studer (Inactive)
            Votes:
            10 Vote for this issue
            Watchers:
            16 Start watching this issue

              Created:
              Updated:
              Resolved: