[GODRIVER-211] Revise connection pooling options on Client/connstring Created: 30/Jan/18 Updated: 28/Oct/23 Resolved: 27/Nov/18 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | Options & Configuration |
| Affects Version/s: | None |
| Fix Version/s: | 0.1.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Golden | Assignee: | Isabella Siu (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Stitch, beta | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Epic Link: | Finalize mongo API | ||||
| Description |
|
Revised:
Original:
|
| Comments |
| Comment by Githook User [ 27/Nov/18 ] |
|
Author: {'name': 'Isabella Siu', 'email': 'isabella.siu@10gen.com'}Message: Change-Id: Ic9b1f10ef3646e535a19a20a53decc0444fe1fe1 |
| Comment by David Golden [ 05/Feb/18 ] |
|
Jesse suggest skipping "minPoolSize" and seeing if anyone actually requests it. |
| Comment by David Golden [ 31/Jan/18 ] |
|
Thank you for explaining it further, Craig. To confirm my understanding, this is what I think you're saying:
Some of my thoughts about where to go from here:
In summary, I think this is what the client should offer as connection string options:
I don't think we need the "waitQueueMultiple" and "waitQueueTimeoutMS" as client can control timeouts/cancellation via contexts objects to avoid blocking indefinitely. |