[DOCS-15464] Investigate changes in SERVER-67094: Implement retry logic in LDAP Created: 04/Jul/22 Updated: 13/Nov/23 Resolved: 12/Oct/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Backlog - Core Eng Program Management Team | Assignee: | Jason Price |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Days since reply: | 1 year, 8 weeks, 2 days ago | ||||||||
| Epic Link: | DOCSP-21764 | ||||||||
| Story Points: | 5 | ||||||||
| 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 TicketLDAP 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. |
| Comments |
| Comment by Githook User [ 12/Dec/22 ] |
|
Author: {'name': 'jason-price-mongodb', 'email': '69260375+jason-price-mongodb@users.noreply.github.com', 'username': 'jason-price-mongodb'}Message:
Co-authored-by: jason-price-mongodb <jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com> |
| Comment by Githook User [ 12/Oct/22 ] |
|
Author: {'name': 'jason-price-mongodb', 'email': '69260375+jason-price-mongodb@users.noreply.github.com', 'username': 'jason-price-mongodb'}Message:
Co-authored-by: jason-price-mongodb <jshfjghsdfgjsdjh@aolsdjfhkjsdhfkjsdf.com> |