Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-15464

Investigate changes in SERVER-67094: Implement retry logic in LDAP

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Done
    • None
    • 6.1.0-rc0
    • manual, Server
    • None
    • 5
    • ServerDocs2022: Jul12 - Jul26
    • a new parameter was added ldapRetryCount, which allows to specify how many retries should LDAP subsytem retry a failed bind or search. Only specific errors are retryable, such as network error or a timeout

    Description

      Original Downstream Change Summary

      a new parameter was added ldapRetryCount, which allows to specify how many retries should LDAP subsytem retry a failed bind or search. Only specific errors are retryable, such as network error or a timeout

      Description of Linked Ticket

      LDAP server is typically a network resource, and as such can fail due to multitude of reasons. This ticket is to implement some sort of retry logic for LDAP calls.

      We could add retry count into LDAP configuration and default it to zero, effectively indicating "no retry" as we have right now.

      Attachments

        Issue Links

          Activity

            People

              jason.price@mongodb.com Jason Price
              backlog-server-pm Backlog - Core Eng Program Management Team
              Githook User Githook User
              Sergey Galtsev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                23 weeks, 5 days ago