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

LDAP connection pool acquisition state should own host list

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.2.6, 4.4.0-rc0, 4.0.18, 4.7.0
    • Security
    • None
    • Fully Compatible
    • ALL
    • v4.4, v4.2, v4.0
    • Security 2020-04-06
    • 11

    Description

      Currently, when acquiring a connection for a set of LDAP hosts, the names of the hosts are owned on the stack. Jobs to fetch connections to all of the hosts are dispatched, and a StrongWeakFinishLine is used to either acquire the first successful connection, or the last unsuccessful. Once the FinishLine completes, connection acquisition is complete. However, there might still be jobs pending which have yet to finish successfully or fail. On failure, we log the name of the server which we failed to connect to. This name is retained by reference. However, the overarching operation might have completed, allowing the name to become invalid.

      Attachments

        Activity

          People

            spencer.jackson@mongodb.com Spencer Jackson
            spencer.jackson@mongodb.com Spencer Jackson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: