[SERVER-53557] Increase connection pool idle timeout Created: 04/Jan/21  Updated: 20/Jan/23

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Benjamin Caimano (Inactive) Assignee: Backlog - Service Architecture
Resolution: Unresolved Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Assigned Teams:
Service Arch
Participants:
Story Points: 2

 Description   

We currently set the connection pool host timeout to 5min here. On the scale of some patterns of work (notably, mirrored reads), this may cause us to unnecessarily drop and recreate pools, which can be an expensive operation when the minimum pool size is set. Pool expiry also emits a mildly concerning message when seen in logs. We should set this host timeout to a larger value ala an hour.

Acceptance Criteria: 

Determine if the existing configurability is sufficient or if we need to change the default timeout (and change if needed). If new grad picks up this ticket, reach out in a team channel for a current answer.

 

 



 Comments   
Comment by Lauren Lewis (Inactive) [ 24/Feb/22 ]

We haven’t heard back from you for at least one calendar year, so this issue is being closed. If this is still an issue for you, please provide additional information and we will reopen the ticket.

Generated at Thu Feb 08 05:31:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.