[GODRIVER-755] Add background goroutine per server to close expired, idle connections Created: 07/Jan/19  Updated: 28/Oct/23  Resolved: 20/May/19

Status: Closed
Project: Go Driver
Component/s: Networking
Affects Version/s: None
Fix Version/s: 1.1.0

Type: Improvement Priority: Major - P3
Reporter: Eric Daniels (Inactive) Assignee: Divjot Arora (Inactive)
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on GODRIVER-932 Update topology.Server type Closed
Epic Link: CMAP compatibility
Case:

 Description   

Link to spec here



 Comments   
Comment by Githook User [ 20/May/19 ]

Author:

{'name': 'Divjot Arora', 'email': 'divjot.arora@10gen.com', 'username': 'divjotarora'}

Message: Change connection pool to a deque and add cleanup routine.

GODRIVER-755

Change-Id: Id9419a4da927eb305e82071efecd89024b2e27dd
Branch: master
https://github.com/mongodb/mongo-go-driver/commit/693fd7f1d6bc4760969c73ee676fdd8bfcebdb57

Comment by Divjot Arora (Inactive) [ 15/May/19 ]

CR: https://review.gerrithub.io/c/mongodb/mongo-go-driver/+/454479

Comment by Divjot Arora (Inactive) [ 10/May/19 ]

eric.daniels My original comment wasn't completely correct. We thought the old and new core packages would use different connection pools, but they actually use the same one in the new design. As a result, we're going to be adding the code for this into the master branch and it will be executed. Note that the code on master in general will be unstable until 1.1.

CC kris.brandow jeff.yemin scott.lhommedieu

Comment by Ian Whalen (Inactive) [ 14/Jan/19 ]

eric.daniels can you help us understand the priority here? Is your current workaround sufficient and can you wait until the CMAP spec is complete?

Generated at Thu Feb 08 08:34:53 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.