[CDRIVER-250] destroy old clients when added back to client pool Created: 11/Nov/13  Updated: 31/Oct/16  Resolved: 31/Oct/16

Status: Closed
Project: C Driver
Component/s: None
Affects Version/s: None
Fix Version/s: 1.4.2

Type: Improvement Priority: Minor - P4
Reporter: Christian Hergert Assignee: Backlog - C Driver Team
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by CDRIVER-416 HA monitoring Closed
Related
is related to CDRIVER-1196 Make client pool a LIFO Closed

 Description   

The client pool will try to hold on to live clients forever. If we have a watermark that we would like to stay below in the connection pool, we should destroy the oldest or unhealthiest connection.

This should likely happen on mongoc_client_pool_push() or potentially on a pop().

Ensure that minPoolSize is respected in the process. minPoolSize is lazy in terms of filling up to minPoolSize, but should not drop below after the connections have been made.



 Comments   
Comment by A. Jesse Jiryu Davis [ 31/Oct/16 ]

Fixed in CDRIVER-1558.

Generated at Wed Feb 07 21:08:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.